Short answer: Shopify Sidekick does not push data into your CRM or your ad accounts. There is no HubSpot connector, no Salesforce sync, no Google Ads upload, no Meta Custom Audience push. What Sidekick does is the part that’s genuinely tedious: translating “our best B2B accounts from the last year” or “lapsed customers who opted into marketing” into a real Shopify customer segment, confirming how many records match, and telling you exactly which fields are available. You export the CSV and do the import yourself.
Once you accept that boundary, this becomes a reliable ten-minute workflow rather than a search for an integration that doesn’t exist.
What Sidekick can actually do here
Sidekick’s half of the job runs entirely inside the Shopify admin:
- Build the segment. Give it a plain-language audience definition and it translates that into Shopify’s segmentation filters — order count, total spent, last order date, product or collection purchased, location, tags, marketing consent.
- Reference B2B companies. If you’re selling wholesale, Sidekick can work with Shopify’s Companies records, not just individual customers — which is usually what a CRM actually wants.
- Confirm the record count before you commit. This is the step people skip and regret. Knowing you matched 47 records instead of the 4,700 you assumed saves a wasted import.
- List the available fields. First name, last name, email, phone, company name, total spent, order count, last order date, default address, tags, consent status.
- Flag unusable records. Customers with no email, or company records with no company name, are dead weight in a CRM import and won’t match on an ad platform at all. Ask Sidekick to surface them so you decide whether to exclude them, rather than discovering the gaps after the import fails.
The CRM path: Shopify to HubSpot, Salesforce, or Pipedrive
Tell Sidekick which CRM you’re importing into, because the CRM’s expected columns shape what you want in the export. Then:
- Have Sidekick build the segment — for example, “B2B companies with an active order in the last 12 months,” or “customers above
[X]lifetime value.” - Confirm the count and field list before exporting anything.
- Export the CSV. Customers → Segments → Export for individual customers, or Companies → Export for B2B accounts.
- Map columns in your CRM’s import tool. Email → Email, Company → Company Name. Shopify’s Total Spent and Order Count usually have no native equivalent, so map them to custom fields like “Lifetime Value” and “Orders.”
- Tag the import batch. Add a source label like “Shopify import
[DATE]” so you can tell these records apart from contacts your sales team added by hand. Without this, you can’t audit where a contact came from six months later.
The ad platform path: Google Ads and Meta
The mechanics are similar, but the fields that matter are different — ad platforms match on identity fields, not commercial history.
- Decide the audience purpose first. A seed list for lookalike targeting, a suppression list to exclude existing customers from prospecting, or a win-back retargeting pool all need different filters. Say which one up front.
- Filter on marketing consent. Ad platforms still expect consented contact data. Filtering at the Shopify segment stage is far easier than scrubbing a spreadsheet later.
- Check the size against platform minimums. Both Google and Meta have minimum thresholds — around 100+ matched contacts is the commonly cited floor — below which match rates stop being meaningful.
- Drop records with neither email nor phone. Those rows can’t match on either platform, so they only dilute your reported match rate.
- Upload manually.
- Google Ads Customer Match: Tools → Audience Manager → Segment → Customer list → upload the CSV, mapping to email, phone, name, country, and zip as prompted. Google hashes the data on upload, so don’t pre-hash it yourself unless you’re going through the API directly.
- Meta Custom Audiences: Ads Manager → Audiences → Create Audience → Customer List → upload the same CSV with the same column mapping. Meta also hashes on upload through the UI.
The part everyone underestimates: decay
There is no live sync in either direction. The moment you export, the clock starts running:
- New customers who would qualify won’t appear until your next export.
- Customers who unsubscribed after the export are still sitting in your uploaded list.
- Ad platform match rates degrade steadily as email addresses go stale.
Pick a cadence and stick to it. Monthly is a reasonable default for ad audiences; CRM imports often work better quarterly, or event-driven when you’re kicking off a specific outbound push. Either way, treat it as a recurring task on someone’s calendar, not a one-time setup.
The bottom line
Sidekick is a segment builder and an export preparer, not an integration layer. The value it adds is upstream of the CSV: correct filters, an honest record count, a field list you can map against, and a heads-up on the records that will fail. The clicking — export, upload, map, tag — stays yours. That split is unglamorous, but it’s fast, repeatable, and it beats hand-writing segment filters and hoping the export contains what you need.