Skip to content
Browse documentation

E-commerce, call tracking and e-mail offers

Copy-paste setups for Shopify, WooCommerce, Ringba, Invoca, Retreaver, Stripe rebills and refunds, Optizmo suppression lists and Zapier / Make / CRMs.

Last updated 4 min read

On this page

The E-commerce and Calls & email tabs under Tracking → Integrations (https://app.trackcrown.com/app/integrations?tab=commerce and ?tab=calls) generate ready-made pixels, plugins and postback URLs for common shop, call-tracking and billing tools. They are presets — code and URLs you install in the other tool — not managed connections: TrackCrown does not log in to Shopify, WooCommerce, Ringba or Stripe.

The presets use your first active tracking domain, the first offer of the workspace and, for admins, the workspace postback token. Non-admins see TOKEN instead ("Postback token hidden"): replace it with the token from Settings → Postback tokens or the advertiser's token. Replace OFFERCODE with the offer you run.

All presets rely on the standard conversion endpoints: /pb (server postback, token required) and /px (browser pixel). See S2S postback, Pixels and Reversals & status updates.

Shopify#

Shopify orders are reported by a custom pixel (Customer events) and reversed by Shopify Flow when an order is cancelled or refunded.

  1. Add the landing-page SDK to the theme. It stores the click ID of the visitor in the first-party atk_cid cookie.
  2. Make sure the offer accepts pixels: Conversion tracking = Server postback or pixel or Pixel only.
  3. In Shopify: Settings → Customer events → Add custom pixel, paste the Shopify custom pixel code from the E-commerce tab, save and connect it.

The pixel subscribes to checkout_completed and calls:

URL
https://trackcrown.com/px?offer_id=OFFERCODE&event=sale&amount=<order total>&currency=<currency>&txid=<order id>&click_id=<atk_cid>

click_id is only added when the cookie holds a valid 32-character click ID.

Reverse cancelled and refunded orders#

In Shopify Flow, create a workflow with the trigger Order cancelled (and one with Refund created) and the action Send HTTP request (method GET) to:

URL
https://trackcrown.com/pb?offer_id=OFFERCODE&txid={{order.id}}&status=rejected&reason=order_cancelled&token=TOKEN

The conversion with this order ID on the offer is rejected and partner reversal postbacks fire.

The E-commerce tab generates this URL with your offer code and token filled in. Keep offer_id in it: a reversal by order ID (txid) is matched within one offer, and without it (and without click_id) the postback is refused with HTTP 400.

WooCommerce#

The WooCommerce card generates a small WordPress plugin (wp-content/plugins/arctrack-conversions.php):

  1. Copy the code, save it as wp-content/plugins/arctrack-conversions.php and activate TrackCrown conversions under Plugins (the file name is a fixed technical name, the same for every brand; keep it).
  2. Keep the file private: it contains the postback token used for reversals.

What it does:

WooCommerce eventRequest
Thank-you page (woocommerce_thankyou)Image pixel /px?offer_id=…&event=sale&click_id=<atk_cid>&amount=<total>&currency=…&txid=<order number>, once per order
Order cancelled, refunded or failedServer-side GET /pb?offer_id=…&txid=<order number>&status=rejected&token=…

As with Shopify, the click ID comes from the SDK's atk_cid cookie, so install the landing-page SDK on the shop.

Call tracking: Ringba, Invoca, Retreaver#

Pay-per-call offers report a converted call as event call. Create an event with code call on the offer's Events tab first.

PlatformSetupPostback URL (GET)
RingbaPartners send traffic to the landing page / number-pool link https://trackcrown.com/r/OFFERCODE/AFFILIATE?sub1=CAMPAIGN. Ringba reads click_id from the landing-page URL as tag User:click_id. Add the pixel to Call converted./pb?click_id=[tag:User:click_id]&offer_id=OFFERCODE&event=call&amount=[Call:ConversionPayout]&txid=[Call:InboundCallId]&token=TOKEN
InvocaPass click_id into Invoca as a marketing data parameter on the landing page; webhook on signal / call end./pb?click_id={{click_id}}&offer_id=OFFERCODE&event=call&amount={{revenue}}&txid={{transaction_id}}&token=TOKEN
RetreaverWebhook on converted call./pb?click_id=[click_id]&offer_id=OFFERCODE&event=call&amount=[revenue]&txid=[call_uuid]&token=TOKEN

All URLs start with https://trackcrown.com. amount is the sale amount (used by percentage payouts); fixed CPA payouts come from the offer's call event.

Stripe rebills and refunds#

TrackCrown has no Stripe webhook endpoint of its own. Forward two Stripe events to the postback URLs below — with a Stripe webhook → Zapier / Make scenario, or from your billing code:

Stripe eventPostback
charge.succeeded (rebill)/pb?offer_id=OFFERCODE&event=rebill&email=CUSTOMER_EMAIL&amount=AMOUNT&currency=CURRENCY&txid=CHARGE_ID&token=TOKEN
charge.refunded (reversal)/pb?offer_id=OFFERCODE&txid=CHARGE_ID&status=rejected&token=TOKEN

Rebills carry no click ID. They are attributed by e-mail ownership: the partner whose conversion first reported this e-mail address on the offer (with email=) owns it for the offer's attribution window. So send email= on the initial sale too, and create an event rebill on the offer. Without an owner, the rebill is stored without a partner. E-mail addresses are only stored as SHA-256 hashes.

E-mail offers: Optizmo suppression lists#

There is no Optizmo sync. The card gives a text for the offer's description:

Text
Suppression list: https://mailer-api.optizmo.net/accesskey/download/YOUR-ACCESS-KEY — scrub every send against it.

Put it in the offer's Description or Restrictions so approved partners see it next to their tracking link, or enter the list link in Suppression list URL (and the advertiser's opt-out page in Unsubscribe URL) under the offer's Advanced tab → Partner-facing details.

Zapier, Make, Segment and CRMs#

  • Out of TrackCrown: outbound webhooks send signed JSON events (conversion.created, conversion.updated, affiliate.signup …) to a Zapier "Catch Hook", a Make scenario, Segment or your CRM.
  • Into TrackCrown: create conversions with POST https://app.trackcrown.com/api/v1/conversions and a REST API key (API reference) or with the S2S postback.

There is no published Zapier app.

Related#

Something unclear or missing in this article?Tell us