Pushground
Pushground is a traffic source (push). Its own documentation: https://www.pushground.com/blog/your-account-manager-replies-how-to-integrate-pushgrounds-s2s-postback.
What it connects
Section titled “What it connects”- Sends your conversions back to Pushground.
- Lists placements to block, for you to export; nothing is sent.
How to connect it
Section titled “How to connect it”No API credentials: the postback carries no secret, only the identifiers set below.
Tracking macros
Section titled “Tracking macros”Each token is a query parameter on the campaign URL; the source replaces its macro with the value when it sends the visitor. The columns say which part of the visit it fills and which report column (v1 to v20) it lands in.
| Parameter | Macro | Fills | Report column |
|---|---|---|---|
click_id | {click_id} | The source’s click id | |
supply | {supply_id} | Placement | v1 (Supply) |
cmp | {campaign_id} | Source campaign | v2 (Campaign) |
creative | {creativity_id} | Creative | v3 (Creative) |
site_id | {site_id} | Site | v4 (Site id) |
source | {source} | Custom value | v5 (Source) |
format | {format} | Custom value | v6 (Format) |
traffic_type | {trafficType} | Custom value | v7 (Traffic type) |
cost | {bid} | Cost |
The campaign URL you paste into the source is the tracking domain, the campaign’s key and the tokens the source fills, in this order (the domain below is an example, and {url_key} stands for the campaign’s own key):
https://trk.example.com/{url_key}?click_id={click_id}&supply={supply_id}&cmp={campaign_id}&creative={creativity_id}&site_id={site_id}&source={source}&format={format}&traffic_type={trafficType}&cost={bid}Cost models, the first the default: from_token (the source’s own cost, passed in a token), cpc (cost per click), cpm (cost per thousand visits).
With from_token, the cost is the value of cost, per visit in USD.
Preview the campaign URL
Section titled “Preview the campaign URL”Campaign URL
Paste the campaign URL into the source's ad. {url_key} stands for the campaign's own key, which the portal fills in; the macros are the source's, which it replaces with each visit's values.
How conversions get back to it
Section titled “How conversions get back to it”Tallyray sends a conversion to Pushground when it enters one of these statuses: approved. A conversion is sent once per status it enters; an adjustment, with revenue moving and its status not, isn’t sent. A conversion older than 30d isn’t sent.
Tallyray’s event kinds, and the name each is sent as. A conversion of a kind not listed isn’t sent:
| Tallyray event | Sent to Pushground as |
|---|---|
sale | sale |
The request: GET https://lupush.com/conversion.
A conversion is sent only when this holds:
=visit.external_click_id != ''Conversions are retried when the source can’t be reached or answers with an error that can pass; see the limits below.
Placements
Section titled “Placements”Placements are the visit’s placement value, as the tokens above fill it.
This template has no block request: Tallyray keeps the blocks as a list you export into the source, and sends nothing.
Limits
Section titled “Limits”- Rate: at most
10/sper connection, 4 at once. - Retries: up to 15 attempts, waiting from
30sand doubling up to6h, longer when the source’sRetry-Afterasks, and never past the conversion’s age limit. - Hosts it reaches:
lupush.com. No other. - What a connection may override:
/tokens,/conversions/events,/conversions/send_on,/cost. Hosts, authentication and requests never are, and an override may only lower the limits.
This page describes version 1 of the Pushground template, the latest published. The version your connection runs is the one your administrators approved, and the portal shows it.