Google Ads needs a Conversion ID and a Conversion label, both of which come from a conversion action you create yourself. The choice you make in step 5 decides whether cPixel can ever add server-side conversions later, and it cannot be changed afterwards without losing the action's history.
Screenshots are from a live account. Account names, IDs, tokens and email addresses are blanked out — yours will show real values in those places.
If you have never set up conversion tracking, this page is mostly an empty state with a New conversion action button. That is the right place to start.
Google pre-ticks Conversions from phone calls for you. Untick it unless you actually want call tracking, or you will spend the rest of the wizard configuring something you did not ask for. Then click Add URL on the website row.
Enter your store domain — your-store.myshopify.com works — and press Scan. Google lists the data sources it found. Tick Google tag. “Not installed yet” is expected and correct: cPixel is what will install it. If it also offers to link a Google Analytics property, leave that alone.
Pick Purchase — when someone completes a purchase or checkout flow. Use one conversion action for purchases only; pointing cPixel at a page-view action would report every visit as a sale.
Google offers Manually with code or Automatically without code. Choose Manually with code. This is the choice that decides whether the action can ever be topped up from a server, and Google does not let you change it later without losing the action's history.
Finish the wizard, then open the conversion action and click Manage beside its data source. Switch to the Use Google Tag Manager tab — it prints Conversion name, Conversion label and Conversion ID as a plain table, which is far easier than digging them out of the tag snippet. Prefix the ID with AW- when you paste it into cPixel.
Conversion actions Google built from a URL rule, and ones imported from Google Analytics, can never be supplemented with server-side conversions. If you point cPixel at one of those, the browser tag will work and the server leg will never be addable. Pick an action you created yourself with the tag, as in step 5.
There is no API token to collect for Google Ads — not now, not later. Server-side conversions go through the Google Ads API, which authenticates by OAuth against a verified application plus a developer token, so it is something cPixel connects on your behalf rather than a key you paste. Be wary of any app whose Google Ads setup asks you to "create a Google Cloud project": that is the OAuth requirement being handed to you, and it is a developer job, not a merchant one. Two things you *can* do now:
XXX-XXX-XXXX number in the top right of Google Ads, beside your email. Every server-side integration needs it, and the API wants it without the dashes. It is an account identifier, not a secret — it identifies which account to write to, and authenticates nothing on its own.Start a live session in cPixel and place a test order. The Google Ads send shows its conversion ID, label and order ID.
cPixel is a Shopify app that tracks your store's events and reports them to your ad platforms — from the shopper's browser and from our servers, through each platform's Conversions API. Browser tracking is free and unmetered on every plan; server-side sending is what the paid tiers add, and it is what keeps conversions arriving when a browser blocks the pixel, drops the tag, or never runs it at all.
Priced on monthly orders, nothing else — not traffic, not your Shopify plan, not the number of platforms you connect. Free installs get 7 days with no cap at all, and on the paid tiers server-side sending is never switched off for going over.