Skip to main content
Connecting Meta pulls campaigns, ad sets, ads, and their spend, so Soran can put cost next to the revenue it attributes.
If you forward conversions to Meta with a destination, Soran sends them from its own servers only. In that case, keep your Meta pixel where it is, and set Shopify’s Facebook & Instagram channel to Standard or Conservative so Shopify does not send a second server copy that Meta cannot pair with Soran’s.

​
How the connection is shaped

Authorizing is three steps rather than one form, because the middle step is what tells Soran what the third can offer:
1

Pick the platform

Choose Meta on the organization’s Connections screen.
2

Provide the credential

Meta’s credential belongs to a system user. This is what Soran stores, once, for your whole organization.
3

Choose ad accounts

The credential can usually read several ad accounts. Pick which ones this property should pull from, on the connection’s own screen.
The credential is scoped to your organization; which accounts are connected is per property. One Meta grant can therefore serve several properties, each reading a different subset — which is the point for an agency.

​
Sync frequency

Choose how often Soran pulls: every hour, every 6 hours, every 12 hours, daily, or weekly. Backfill reaches every day of spend Meta still reports.

​
Getting the exact ad, not a name match

Pulling spend tells Soran what you spent. It does not, on its own, tell Soran which ad a click came from — matching on campaign names is guesswork. Tagging your ad URLs fixes that.

URL tagging

Tag Meta ad URLs so clicks join to the exact ad.