Relay deliveries: every send and the platform's answer
On this page
Deliveries lists every conversion Relay sent to your ad platforms, and each platform's answer. Open it from the sidebar: Relay > Deliveries.
The table
Each row is one conversion sent to one ad account, newest first.
- Event: the name the conversion was sent as, with its order and its source.
- Ad account: where it went.
- Outcome: what happened, with the platform's answer underneath.
- Value: the value sent.
- Sent: when it left.
Click the dates to choose other days. Search by event or order, or filter by Ad account, Outcome and Source.
What each outcome means
- Accepted: the platform took the conversion.
- Accepted in test: the platform took it as a test event. The ad account is in Test, so the platform does not count it.
- Failed: the send did not go through. The line underneath says why.
- Refused: the platform refused the conversion. The line underneath says why.
- Taken back: Relay withdrew a conversion it had sent, for example after a refund.
- Held back: Relay did not send the conversion. The line underneath says why. Held back deliveries are hidden until you pick them in the Outcome filter.
The platform's answer
Under an accepted conversion the page says what the platform did with it.
- Counted by the platform: the platform's own count includes it.
- Waiting for the platform's count: the platform has still to report it.
- The platform counted fewer than Relay sent: the platform's count is lower than what Relay sent.
- The platform counts it with your pixel's events of the same name: the platform reports one count for Relay's event and your pixel's.
- The platform does not report its count: the platform gives no count to read back.
Why a conversion was held back
- The visit was invalid traffic: Tapper Block flagged the visit.
- Cancelled or refunded: the order was cancelled or refunded before it was sent.
- The buyer did not click this platform: the ad account takes a sale only when the buyer clicked an ad of its platform. You choose this under Send sales to on the ad account's Relay settings.
- Your store app already sends it: the store's own app sends the same sale, so Relay leaves it.
- Consent was withdrawn, The buyer's consent is not on record or Recorded before consent: the buyer's consent does not allow sending.
- Nothing the platform can match on: the conversion carries no click ID, e-mail or phone the platform could use.
- Older than the platform takes: the conversion is older than the platform accepts.
Why a send failed
- The connection to the ad platform has expired: reconnect the ad account on Setup > Ad accounts.
- The ad account needs a change on the ad platform: finish the step the ad platform asks for, then retry.
- The ad platform was busy or did not answer: Relay tries again by itself.
- The ad platform refused this event: open the delivery to see what was sent.
One delivery's page
Click a row to open the delivery. The page shows Sent, Value, Tries, With your pixel and the platform's answer, then every field Relay sent, such as the conversion, the order ID, the value, the currency and the click ID. E-mail and phone show as hashed, sent or not sent.
With your pixel reads one of two ways: the conversion is paired with your pixel's purchase, so the platform counts it once, or it is Relay's own event and is not paired with your pixel.
A delivery that failed and can be sent again shows a Retry button.
Messages on this page
- Your deliveries show here: Relay has sent nothing for this entity. Click Open Events and choose where your events go.
- Nothing was sent: Relay decided not to send this conversion, so no fields went to the platform.
Related
Was this helpful?
Still need help?
Chat with our team and mention this article.