Destinations
A destination sends your conversions to an ad platform from the server. Each platform can have several connections (pixels, data streams, ad accounts). Each one starts off and in test mode: events go to the platform's test tool, or are only checked, and nothing counts until you go live and switch sending on.
Step-by-step setup for each platform is on Platform setup. Event names and your own rules are on Event aliases and rules. Sales made in store or by phone are on Offline sales.
Platforms
| Platform | Sends to | One connection is a | You need | Oldest event accepted |
|---|---|---|---|---|
| Google Ads | Google Ads (Data Manager) | conversion account | Google sign-in · Google Ads account id (10 digits) · Conversion action id | 90 days |
| Meta | Meta Conversions API | pixel | Pixel / dataset id · Conversions API access token | 7 days |
| Pinterest Conversions API | ad account | Ad account id · Conversions access token | 7 days | |
| Reddit Conversions API | pixel | Pixel id · Conversions API access token | 7 days | |
| Snapchat | Snapchat Conversions API | pixel | Pixel id · Conversions API token | 7 days |
| TikTok | TikTok Events API | pixel | Pixel code · Events API access token | 7 days |
| Microsoft Advertising | Microsoft Advertising (UET Conversions API) | UET tag | UET tag id · Conversions API token | 90 days |
| Google Analytics 4 | Google Analytics 4 | data stream | Measurement ID (G-…) · Measurement Protocol API secret | 3 days |
| LinkedIn Conversions API | ad account | Conversions API access token | 90 days | |
| X | X Conversions API | pixel | Pixel id · Pixel access token | 7 days |
| Quora | Quora Conversion API | ad account | Ad account id · Ad account currency · Conversion API token | 7 days |
| OpenAI Ads | OpenAI Ads Conversions API | pixel | Pixel id · Conversions API key | 7 days |
| Google Enhanced Conversions | Google Enhanced Conversions (web) | tag conversion | Google sign-in · Google Ads account id (10 digits) · Conversion action to improve (id) | 1 day |
Several pixels per platform
- Settings → Destinations lists every platform. Open one to see its pixels in a table: name, the platform's id, status, a Sending switch, events accepted in the last 7 days and when the platform last accepted one.
- Every pixel of a platform gets the same events. Each has its own ids, token, test mode and settings. New ones are named after the platform, for example "Meta pixel 1", "Meta pixel 2" or "GA4 data stream 1". You can rename them.
- Add pixel (Add data stream, Add ad account… after the platform's own word) opens the connect page: where to find the values, step by step; a name; the ids and token; then Save and continue, which tests the connection. The new pixel starts off and in test mode.
- Sending: switch it off to stop sending to one pixel. The other pixels of the platform keep sending.
- Send a secure link: a one-time link for whoever holds the account. It fills in a pixel you pick, or adds a new one, without a Trakbolt login. Not for Google Ads or Google Enhanced Conversions, which need a Google sign-in.
- Disconnect (Settings tab): stops sending and removes the pixel from the lists. Its delivery history stays in the delivery log. Events still waiting to be sent are skipped.
A pixel's status is one of: Not set up, Sending off, Failing, Needs a test, Test mode, Live. On the list of platforms, a platform shows its most urgent pixel.
The pixel tabs
| Tab | What it has |
|---|---|
| Overview | The last 7 days: events that apply to the pixel, how many were sent and how many the platform accepted; the match keys sent on purchases; the connection. Diagnostics groups the errors and warnings of the last 7 days by reason, with how often and what to fix; expected skips (free orders, no click from this platform…) come last. Platform quality score: the platform's own score, fetched with the saved token and kept 6 hours, for Meta (Event match quality) and Pinterest (Event quality score). Other platforms have no public API for it. |
| Events | Each of your events and the platform event it is sent as (its alias), with the per-event id where the platform needs one. Switch an event off to stop sending it. Below: built-in rules and your own event rules. |
| Test & activity | Send a test event (with a Test ID for that one send if you like), Go live or Back to test, and the latest sends with the platform's answer. |
| Settings | The ids and token, who is sent and the value sent, order rules, match keys, opted-out shoppers, product details, offline sales, name, secure link and disconnect. |
Test mode works differently per platform; some platforms have none. See the test mode line of each platform on Platform setup.
Who is sent
By default an ad platform only receives the sales its own clicks led to (its click id or campaign in the buyer's journey). Google Analytics 4 is a reporting destination and receives every sale.
Retargeting
Each pixel has a Retargeting switch (Settings tab). On, every lead and buyer is sent to that platform with hashed email and phone, so you can build audiences there, for example people who signed up and did not buy, and leave buyers out. People who refused consent, test people and bots are never sent. The platform's own reports may count more conversions while it is on; Trakbolt's reports do not change. On a healthcare workspace an admin confirms the approval when switching it on, and only neutral event names are sent (step_1, step_2…). Audience lists can also be synced to Meta, Google Ads, Snapchat, Pinterest and Reddit (Audiences).
What is sent
- The event name you mapped, the event time, the order id, value and currency.
- Match keys: hashed email and phone (SHA-256, normalised; each platform in the format it expects), the platform's own click id, and the browser's user agent where the platform uses it.
- On healthcare workspaces: neutral event names and the site's address without its path. Never a product, condition or plain-text contact detail.
Order rules
Settings tab → Orders. Each pixel has its own. A skipped order shows its reason in the delivery log.
| Setting | Choices | Default |
|---|---|---|
| Order value |
| Total |
| Skip free orders | Orders worth 0 are not sent. | On |
| Minimum order value | Orders below it are not sent. It is in the store's currency and only compared with orders paid in that currency. | None |
| Currency sent |
| Shopper's currency |
| Lead events |
| No value |
| Sign-up events |
| No value |
Lead events is shown only while the workspace has a value of a lead (Settings → General; lead and hybrid workspaces, never healthcare), on Meta (custom_data.value + currency), Pinterest (custom_data.value + currency), Snapchat (custom_data.value + currency), TikTok (properties.value + currency). Other platforms take the value set on their own conversion action.
Match keys
Settings tab → Customer data. Switch a key off to send less. Settings can only take keys away; health-data rules always apply on top. A key the platform does not take is shown but has no effect.
| Key | What is sent |
|---|---|
| Hashed (SHA-256) before it leaves Trakbolt. | |
| Phone | Hashed (SHA-256) before it leaves Trakbolt. |
| Customer ID | Your customer or patient id, hashed with this workspace's own salt (external id). |
| Name | First and last name, hashed (SHA-256). Only when the client's data sharing allows names and contact details are kept. |
| Address | City, state, zip and country, hashed (SHA-256). Only when the client's data sharing allows addresses and contact details are kept. |
| IP and browser | The browser's user agent and IP address from its latest visit (W138: the IP is kept encrypted, only for the lookback window, and never for visitors who refused consent). |
Send people a platform can only partly match (off by default): with no email, phone or click id, the event is still sent where the platform accepts fewer keys (Pinterest: the IP address and browser together). It works only when your Trakbolt support has allowed it for your account.
Opted-out shoppers
A shopper whose latest visit refused consent. Each pixel chooses (default: Send with limited use):
- Send with limited use: Sent with the platform's limited-use flag; not sent where the platform has none.
- Don't send: Shoppers whose latest visit refused consent are never sent to this pixel.
| Platform | Match keys it takes | Opted-out shoppers with limited use |
|---|---|---|
| Google Ads | Email, Phone | Sent, consent block set to DENIED |
| Meta | Email, Phone, Customer ID, Name, Address, IP and browser | Sent, Limited Data Use (data_processing_options LDU) |
| Email, Phone, Customer ID, Name, Address, IP and browser | Not sent: the platform has no limited-use flag | |
| Email, Phone, Customer ID, IP and browser | Not sent: the platform has no limited-use flag | |
| Snapchat | Email, Phone, Customer ID, Name, Address, IP and browser | Not sent: the platform has no limited-use flag |
| TikTok | Email, Phone, Customer ID, IP and browser | Not sent: the platform has no limited-use flag |
| Microsoft Advertising | Email, Phone, Customer ID | Not sent: the platform has no limited-use flag |
| Google Analytics 4 | None (click and visit ids only) | Sent, consent set to DENIED |
| Email, Customer ID | Not sent: the platform has no limited-use flag | |
| X | Email, Phone, IP and browser | Not sent: the platform has no limited-use flag |
| Quora | Email, IP and browser | Not sent: the platform has no limited-use flag |
| OpenAI Ads | Email, Phone, Customer ID, IP and browser | Sent, opt_out set to true |
| Google Enhanced Conversions | Email, Phone | Not sent: the platform has no limited-use flag |
Product details
Settings tab → Products: what an event carries about its items. Sent on purchases (the order's items) and on product views, add to cart, checkout started and any other event your server sends with items (server events API: items, up to 50 per event). The site script sends no items. Default: None, with Product ID as the id.
| Product details | What is sent |
|---|---|
| Full | Product ids with name, category, price and quantity, where the platform takes them. |
| IDs only | Product ids with their quantities and the number of items. |
| None | No product data: value, currency and order id only. |
| Product id sent | Which id |
|---|---|
| Product ID | Your product id (items[].id). Sent as a product group where the platform asks. |
| Variant ID | Your variant id (items[].variant_id). Items without one are left out. |
| SKU | Your SKU (items[].sku). Items without one are left out. |
Use the id your platform's catalog is keyed on. Items come from your order's items (server events items, CSV imports, offline sales). Healthcare workspaces: always None, and the setting is locked. a product name or id can reveal a condition, so no product data is sent from this workspace.
| Platform | Product fields sent | Full adds |
|---|---|---|
| Google Ads | cart data items (merchant product id, quantity) | unit price |
| Meta | content_ids, contents (id, quantity), num_items, content_type | item price |
| content_ids, contents (id, quantity), num_items | item price, name, category | |
| products (id, quantity), item count | name, category, item price | |
| Snapchat | content_ids, contents (id, quantity), num_items | item price |
| TikTok | contents (content id, quantity), content_type, num_items | name, category, price |
| Microsoft Advertising | No product data from Trakbolt | — |
| Google Analytics 4 | No product data from Trakbolt | — |
| No product data from Trakbolt | — | |
| X | contents (content_id, num_items, content_group_id), number_items | content_name, content_type (category), content_price |
| Quora | No product data from Trakbolt | — |
| OpenAI Ads | data.contents (id, quantity, group_id) | name, amount (unit price, minor units), currency |
| Google Enhanced Conversions | No product data from Trakbolt | — |
Once-per-visit events
On a platform's page, under its pixels: Send bulk events once per visit. It applies to every pixel of that platform. Only the first of each listed event in a visit is sent; later ones in the same visit are logged as skipped ("already sent once this visit"). It is off by default; the suggested events are item_list_viewed and product_viewed. Events of shoppers with no known visit are always sent.
Event names
Each standard event is sent under the platform's own name. Healthcare workspaces use the neutral set. Change them on a pixel's Events tab (see Event aliases and rules).
| Platform | Standard | Healthcare |
|---|---|---|
| Google Ads |
|
|
| Meta |
|
|
|
| |
|
| |
| Snapchat |
|
|
| TikTok |
|
|
| Microsoft Advertising |
|
|
| Google Analytics 4 |
|
|
|
| |
| X |
|
|
| Quora |
|
|
| OpenAI Ads |
|
|
| Google Enhanced Conversions |
|
|