Skip to main content
Conversions lists every delivery attempt we made to an ad platform, and the rules that produced them. One event produces one row per rule, so a workspace with three ad platforms and three rules shows three rows for a single purchase.

​
Read the table

Hover the status badge to read the HTTP status and the attempt number. The toolbar total counts each event_id once, not each row. A three-platform workspace therefore sees one $50 order as $50. Non-USD values are added at face value, without a currency conversion. Select a value inside a row to add it as a filter.

​
Open one delivery

  1. Select a row to expand the summary.
  2. Open the row for the full detail.
  3. Read request_payload to see exactly what we sent.
  4. Read response_body to see exactly what the ad platform replied.
  5. Compare the value and currency against the original revenue record.
The response body is the authority on a failure, because we store the ad platform’s own error text rather than a paraphrase.

​
Rules

Select manage rules to open the rule list. Each rule shows three counts. matched far above sent means the delivery stage is broken, not the tracking. Open a rule to see its trigger, destination, value settings, mappings, and its last delivery attempts under recent activity.
Do not enable two rules with the same trigger event and the same destination asset. Each rule delivers separately, and the ad platform counts the conversion twice. To split one trigger event between rules, give each rule a condition under only send when….

​
Create a rule

1

Open the editor

Select manage rules. Select new rule.
2

Set the trigger

Fill rule name. Pick the trigger event from the workspace’s real event names.
3

Set the destination

Pick the target platform. Pick the destination asset. Select next.
4

Map the event

Pick the platform standard event. Set value and currency.
5

Optional: limit the events

Under only send when…, select condition. Pick a property, an operator, and a value. The line above the rows shows how many recent events of the trigger match. See Send only some events.
6

Save

Select save. Enable the rule.
The editor blocks a save when the mapping cannot work. It rejects these three combinations.

​
Send only some events

A rule sends every event that matches its trigger event. Conditions limit the rule to events whose properties match. Use them when one event name comes from two places and each place needs its own rule. Example: a store sends checkout_started from its Shopify checkout and from its own Stripe checkout page. The Stripe page sets the property checkout to stripe. A rule for the Stripe page uses one condition: The rule then skips every Shopify checkout_started event. A skipped event writes no row under the rule. Every condition on a rule must match. A rule holds up to 5 conditions. The rule’s detail view lists them under Only when. Before you save, read the count above the rows. 21 of 51 recent events means the rule would have sent 21 of the last 51 trigger events. A count of 0 means the property name or the value is wrong. For each operator and how a missing property is treated, see Property conditions.

​
Verify

  1. Select manage rules. Open your rule.
  2. Select send test event.
  3. Confirm the rule’s sent count went up by 1.
  4. Open the newest row under recent activity.
  5. Confirm response_body carries the ad platform’s acceptance field.
Meta and TikTok refuse a test until the rule carries a Test Events code. The row then reads skipped with the reason test_event_code_required.

​
When it does not work

​
Next