Supported · ready to use
HilltopAdsMeetROAS
Put the MeetROAS campaign URL into HilltopAds, then paste the provider-generated conversion settings back into MeetROAS. Choose Custom or Other tracker when no MeetROAS tile is listed.
Can I use it?
Ready to use after one Postback test. MeetROAS enables production delivery after HilltopAds Results shows closed.
What to copy and where to paste it
| Copy | Paste into |
|---|---|
| The complete MeetROAS campaign URL containing {{ctoken}} | HilltopAds Final Destination URL |
| The complete account-generated HilltopAds postback URL | MeetROAS Campaign → Conversion integrations |
Interface map
Trackers / Manage Campaigns → Postback test
Paste the complete MeetROAS campaign URLURL must keep{{ctoken}}
Campaign → Conversion integrations
Paste the Trackers URL once and create Main plus event-specific Micro conversions in one click✓ Finally confirm the conversion in HilltopAds
What you need
| Provider area | Trackers / Manage Campaigns → Postback test |
|---|---|
| Click macro | {{ctoken}} |
| Return method | HTTPS GET Postback |
Copy the account URL on trackhta.com/close/ and keep token={{ctoken}} with advertiserId. Main has no goal; MeetROAS normalizes Micro to goal=<event_key>.
Setup steps
- Create or open a MeetROAS Campaign whose traffic source is HilltopAds, then copy the generated campaign URL.
- Use the MeetROAS campaign URL as Final Destination URL; {{ctoken}} is already included.
- Copy the account URL from Trackers. Main has no goal; MeetROAS adds the event goal for each Micro conversion.
- In MeetROAS, paste the Trackers URL once, then create PWA install as Main and the other events as Micro in one click. If the primary goal differs, revoke and replace only the ambiguous binding. Every full URL remains visible and editable.
- Run Postback test beside Final Destination URL in Manage Campaigns, open the test link, and trigger the event. After MeetROAS shows the send, refresh Trackers → Test Conversion and finish only when Results shows closed.
If the provider does not list a MeetROAS tile, use Custom, Other tracker, or the provider's generic postback option.
Events and money
Each Campaign may have at most one active Main; use Micro for other events. price is conversion cost and receives Partner Event price only; currency may appear only with price.
Destination money → upstream parameter reference
Direction: destination → MeetROAS Partner Event API → attributed source. value is revenue; price is acquisition cost; currency is declared by the destination. — means this MeetROAS connector does not project that field, not that the upstream lacks it. URL money columns show optional template placeholders: replace only when both template parameter and destination amount exist; omit when the amount is absent. No automatic parameter insertion, substitution between amounts, or FX conversion. Registration and login cannot carry money.
| Source | value → | price → | currency / missing-value rules |
|---|---|---|---|
| HilltopAds | — | price={{price}} | currency={{currency}} is passed through; template must also contain price. Missing price removes both; missing currency removes currency only; no FX conversion |
Click, Goal and slot defaults
The upstream expands the campaign macro into a real click ID, which MeetROAS returns; it is not the destination's mrc_. These are defaults for new bindings; existing manual bindings are not overwritten. Obtain account identifiers and URLs from each provider; never infer events from slot numbers or tokens.
| Source | Campaign macro / parameter | Outgoing click field | Event / Goal mapping |
|---|---|---|---|
| HilltopAds | {{ctoken}} | token={{ctoken}} | With no existing Main: pwa_install → Main (no goal), other public events → Micro (goal=<event_key>). With an existing Main, all new defaults use Micro |
How to confirm success
Run Postback test beside Final Destination URL in Manage Campaigns, open the test link, and trigger the event. After MeetROAS shows the send, refresh Trackers → Test Conversion and finish only when Results shows closed.
- The provider generates the test click and MeetROAS attributes it to the correct source.
- MeetROAS shows the event as received and an identical retry does not create a duplicate.
- Finally, confirm that HilltopAds received the conversion. The provider dashboard is the final result.
Cautions
- Main must not contain goal. A Micro goal is derived from the MeetROAS event key, not an arbitrary label in an old URL.