Common questions about Ads IQ, the tab in your Shopflo dashboard that connects your checkout data to your Meta stack. For the full walkthrough, see How to Set Up and Use Ads IQ (Meta) on Shopflo.

→ Open the Ads IQ tab in your Shopflo dashboard.

The tab in your Shopflo dashboard that connects your checkout data to your Meta stack, so you can see the full ads-to-order funnel per campaign, verify that your events are actually reaching Meta, and choose which checkout signals Meta gets to learn from.

It is live now. Open the Ads IQ tab on your Shopflo dashboard and connect your Meta account.

Ads IQ is included in your existing Shopflo plan.

No. No script, no tag, no theme change, no deploy. The entire setup is a Meta login and a pixel selection inside the dashboard.

Under two minutes to connect. Allow a few hours before the first data populates the Events Health and funnel views.

No. Ads IQ reads data Shopflo already captures at checkout and sends events server-side. Your theme, your apps and your existing Shopify setup are untouched.

No. Leave it exactly as it is. Do not remove it.

No. Shopflo sends the same event ID on every event it fires. Meta deduplicates on that event ID: when it receives two events carrying the same ID and the same event name, it keeps one and discards the other. So even with the same pixel configured in both the Integrations tab and the Ads IQ tab, Meta counts each event once.

Because Ads IQ is where everything lives: custom event configuration, pixel routing, event health, EMQ scores and the campaign funnel. Running both is harmless, but once you have confirmed in Events Health that your events are landing, switching off the Integrations tab connection keeps your Meta setup in one place instead of two.

No. Nothing breaks if you leave both running indefinitely. Switch when you are comfortable.

The Integrations tab connection sends events. Ads IQ sends events and adds the control and diagnostic layer on top: which events fire, to which pixel, whether Meta received them, how well they matched, and what each campaign did on your store.

The same way. Any other tool sending events to your pixel continues to work. Where those events overlap with Shopflo's, Meta's event ID deduplication resolves them. A Meta count meaningfully higher than the Shopflo count in the Events Health view is a signal that another source is writing to the same pixel, worth auditing.

Meta will show you the exact list on its consent screen. In plain terms, Shopflo requests read access to your ad performance data (to identify your campaigns and attribute sessions to them), read and write access to your pixel's event data (to send events and read back delivery statistics and match quality), and audience management access (requested up front so you do not have to re-authorise later as Ads IQ expands).

No. Ads IQ has no ability to create, edit, pause or fund campaigns. It reads performance data and writes event data. Your ad account controls remain entirely yours.

No. You log in on Meta's own screen. Shopflo receives an access token from Meta, never your credentials.

Yes. You can revoke Shopflo's access from Meta Business Settings at any time, or disconnect from the Ads IQ tab. Events stop flowing through Ads IQ from that point.

The connection badge changes to Token Expired and prompts you to re-authenticate. Re-authenticating preserves your event configuration and pixel routing. Nothing needs to be set up again.

Yes. Multi-pixel selection is supported, which matters if you run separate pixels per brand or per campaign objective. You can also route specific event types to specific pixels.

Someone with Admin rights on the Meta ad account and the pixel. An Analyst role will not complete the flow.

Last click. A session, and any order that comes out of it, is credited to the last campaign the shopper clicked before that session began. One session maps to one campaign, so nothing is double counted anywhere in the funnel.

Ads IQ reports on last click only, so every number in the funnel traces back to a single campaign, consistently. Multi-touch and first-click modelling are not part of this first cut.

Because they measure different things. Meta's default reporting also credits view-through conversions and uses multi-day click windows, so an order can be attributed to a campaign in Meta that Ads IQ credits to a different one, or to no campaign at all. Neither is wrong. Use Meta Ads Manager for the decisions you make inside Meta's own model. Use Ads IQ to compare campaigns against each other on what actually happened on your store, and to find where in the funnel a campaign is losing people.

Two ways. First, coverage: browser pixels miss a meaningful share of conversions because of iOS restrictions, cookieless browsers and ad blockers. Shopflo sends events server-side from inside the checkout, which is not subject to those losses. Second, depth: your previous setup could tell you a purchase happened. Ads IQ tells you which campaign brought the session, every step the shopper took, how they paid, and whether Meta actually received and matched the event.

Yes. Sessions, product page views, add to carts, checkouts initiated and completed orders are all counted from events Shopflo observes directly on your store, not inferred or modelled. When a campaign row says forty orders, forty orders were placed at your checkout off that campaign's traffic.

No. Shopflo captures UTM parameters at checkout initiation and carries them through the checkout. For the campaign-level funnel to join cleanly, we recommend setting utm_content to the Meta campaign ID at the ad level in Meta's URL parameters. Joining on campaign name works too, but breaks whenever a campaign is renamed. Your CSM can help you set this up once.

Not in this first cut. The funnel starts at the session, which is the first step Shopflo can observe directly, and runs through to the completed order. Keep using Meta Ads Manager for the ad-delivery side of the picture.

Meta scores every event from 0 to 10 on how confidently it could match that event to a real Meta user. A higher score means Meta's optimiser can attribute the event to a person and learn from it. A low score means the event effectively goes to waste.

Because of where the event fires. A browser pixel event on a product page has very little to identify the shopper with. By the time a shopper reaches Shopflo checkout, we already hold their name, email, phone number and address, so our server-side events carry far more matchable identifiers.

No. Meta only computes a score for events with enough volume. Low-traffic custom events will often show blank until volume builds.

Something other than Shopflo is also sending that event to the same pixel, typically a leftover pixel snippet in your Shopify theme or another app. It is worth auditing the pixels on your store. This is not caused by Ads IQ, and it is not caused by running both the Integrations tab and Ads IQ connections, since those deduplicate on event ID.

A small gap is expected, from deduplication and Meta's processing delay. A sustained gap of more than roughly 15 percent against your 30-day average is worth flagging to us.

When a browser blocks third-party cookies, which is common on Safari and in incognito sessions, browser-side pixels lose the session entirely. Shopflo's events are sent server-side from the checkout, so those orders still reach Meta regardless.

Standard Meta events tell Meta that a purchase happened. Custom events tell Meta what kind of purchase it was: prepaid or COD, first time or repeat, full price or discounted.

Yes. Prepaid Purchase and COD Purchase are both available. Separating them is a common starting point for Indian D2C brands, since it lets you optimise on prepaid purchases specifically rather than paying acquisition cost for orders that come back as RTO.

Prepaid Purchase, COD Purchase, New Customer Purchase, Repeat Customer Purchase, Purchase with Discount, Coupon Applied, Coupon Failed, Payment Initiated, Payment Failed, Payment Method Selected.

No. Every custom event is off by default and you enable each one individually. Nothing is sent to Meta without you switching it on.

No. Enabling an event is a toggle in the dashboard. Shopflo reads the configuration at runtime, so there is no code change and no deploy.

Enable it in Ads IQ, wait for the first events to land, then in Meta Events Manager go to Custom Conversions, create a new one, select your pixel, choose Custom Event, and pick the Shopflo event from the dropdown. It appears there only after Meta has received at least one instance. Once created, it is selectable as a campaign optimisation objective. The setup guide has the full walkthrough.

Two or three to start. Meta needs roughly 50 conversions per week on an event before its optimiser learns reliably from it, so spreading thin across ten events works against you. Also note Meta caps an ad account at 100 custom conversions in total.

For most brands, New Customer Purchase and Prepaid Purchase. The first stops your acquisition budget being spent re-buying customers you already own. The second stops you optimising toward orders that carry RTO risk.

No. Custom events are additive. Your standard Purchase event continues to fire exactly as before, and existing campaigns optimised on it are unaffected.

Yes. Pixel routing lets you assign a specific pixel per event type, overriding the default you set during setup.

The same categories of identifier that any Meta conversions integration sends, used for matching the event to a Meta user, plus the event parameters shown in the event preview. You can see the exact payload for any event before enabling it, using the preview in the Events Manager.

Yes. Personal identifiers are SHA-256 hashed before they leave Shopflo systems, in line with Meta's requirements. Raw personal data is not passed through in the clear.

Shopflo's Meta integration is built to the same hashing and data-minimisation standards that Meta's own conversions integrations require, and Shopflo remains your processor for this data. Compliance for your store also depends on your own privacy notice and consent posture, so if you have a specific DPDP question for your legal team, raise it with your CSM.

Almost always a permissions issue. Confirm you are logging in with an account that has Admin rights on both the ad account and the pixel in Meta Business Settings, not Analyst.

Your Meta account has no pixel or dataset created. Create one in Meta Events Manager, then return to Ads IQ and refresh.

Allow a few hours after connecting. If it is still empty after that, check the connection badge for a token issue, then confirm you have selected a pixel.

Meta only lists an event once it has received at least one instance of it. Confirm the event is enabled in Ads IQ and that Events Health shows a non-zero count, then check again.

Check the connection badge first, since token expiry is the most common cause. If the connection is healthy, raise it with your CSM with the date range and pixel so we can trace it.

Reply to the Ads IQ email or reach out to your CSM. If it is an event-delivery or attribution question, include your pixel ID and the date range you are looking at, which lets us trace it immediately. You can also reach us at support@shopflo.com.