DarkRoseDating marketing
Campaigns & campaign links
Create a campaign, add its MTL and VTL links, then attach tracking once for the whole campaign.
One campaign controls all of its links
The campaign stores the incoming click ID and the conversion destinations. Every link below automatically uses that same setup.
1. Campaign→2. Add MTL/VTL links→3. Attach postbacks once
Your campaigns
Select a campaign to manage its links and conversion tracking.
| Campaign | Traffic source | Country | Campaign links | Tracking | |
|---|---|---|---|---|---|
| ExoClick · UK Golden GlamDR-EXO-UK-001 | ExoClick | United Kingdom | 1 MTL · 3 VTL | 2 events active | |
| EvaDav · AU ModelsDR-BEMOB-AU-002 | EvaDav via BeMob | Australia | 1 MTL · 4 VTL | BeMob attached | |
| Google Search · UKDR-GADS-UK-003 | Google Ads | United Kingdom | 1 MTL | Draft |
Selected campaign
Active
ExoClick · UK Golden Glam
Campaign ID: DR-EXO-UK-001 · DarkRoseDating · United Kingdom
cidReceives ExoClick’s {conversions_tracking}external_click_idUsed in every event postback1
Campaign links
These links can point to different models. Tracking does not need to be configured again for each link.
| Type | Link name | DarkRoseDating campaign URL | Uses campaign tracking |
|---|---|---|---|
| MTL | Main UK landing pageDefault campaign entry | https://www.darkrosedating.com/lp005/?ref_ids=lpWWpJalmqacmpeon6CSlKeiYZJk&cid={conversions_tracking} | ✓ Inherited |
| VTL | Golden GlamModel route: gg | https://www.darkrosedating.com/lp005/?ref_ids=lpWWpJalmqacmpeon6CSlKeiYZJk&srcm=gg&cid={conversions_tracking} | ✓ Inherited |
| VTL | LilithModel route: lilith | https://www.darkrosedating.com/lp005/?ref_ids=lpWWpJalmqacmpeon6CSlKeiYZJk&srcm=lilith&cid={conversions_tracking} | ✓ Inherited |
| VTL | Golden Glam profileDirect model page | https://www.darkrosedating.com/profile/Golden-Glam50s?cid={conversions_tracking} | ✓ Inherited |
2
Postbacks attached to this campaign
Redsoft knows which URL to call because these destinations are saved on campaign DR-EXO-UK-001.
Registration
Triggered after a verified DarkRoseDating registration.
http://s.magsrv.com/tag.php?goal=e43b3ba9187ce9d08b25f2a51f33b876&tag={external_click_id}Purchase
Triggered after a verified successful payment.
http://s.magsrv.com/tag.php?goal=10151cea167cf2cc1156ca7a033a9fa7&tag={external_click_id}What happens: a visitor opens any link above → ExoClick inserts its click ID → Redsoft stores it with this campaign → registration or purchase fires the correct campaign postback.
Marketing
Postback configurations
Manage the event destinations attached to each DarkRoseDating campaign.
The campaign—not the click ID—selects the postback
The click ID identifies the visitor. The campaign relationship tells Redsoft whether to call ExoClick, BeMob, Google Ads, or another destination.
Campaign link→Stored click ID→Campaign event destination
EXActive
ExoClick · UK Golden Glam
Custom S2S · DR-EXO-UK-001
- Campaign links
- 4
- Events
- Registration, Purchase
BMActive
BeMob · AU Models
Custom S2S · DR-BEMOB-AU-002
- Campaign links
- 5
- Events
- Registration, Purchase
GDraft
Google Search · UK
Google Ads browser event · DR-GADS-UK-003
- Campaign links
- 1
- Events
- Purchase
Campaign tracking
SavedExoClick · UK Golden Glam
Direct ExoClick S2S goals for every link in campaign DR-EXO-UK-001.
1
Example URLIncoming click
All links in this campaign include the source token and send the populated value to Redsoft.
https://www.darkrosedating.com/lp005/?ref_ids=lpWWpJalmqacmpeon6CSlKeiYZJk&srcm=gg&cid={conversions_tracking}ExoClick replaces {conversions_tracking} with its real click token. Redsoft receives cid=ABC123 and stores ABC123 internally as external_click_id.
2
Campaign conversion events
Each slot determines exactly when Redsoft calls the saved URL. These events cover every MTL and VTL link in the campaign.
RegistrationAfter verified account creation
PurchaseAfter verified successful payment
1
Google Ads browser event
This is browser-based tracking, not S2S. Paste Google’s generated event snippet and Redsoft extracts the send_to value.
Extracted send_toWaiting for a snippet…
Transaction IDAutomatically populated with Redsoft order ID
2
Future integrationGoogle Ads server-side integration
A separate advanced integration requiring Google account authorization through OAuth.
- Google Ads API access and developer credentials
- The advertiser’s account and conversion-action IDs
- Capturing identifiers such as
gclid,gbraid, orwbraidfrom the campaign link - Storing that identifier with the visitor
- Uploading conversions through Google’s API
- Correct timestamps, values, currencies, consent data and transaction IDs
- Handling API errors, retries, duplicate uploads and attribution windows
Technical reference
Redsoft values & naming
A single internal language that works with ExoClick, BeMob, Voluum, RedTrack, and custom postbacks.
External platforms use different names; Redsoft stores one standard value
For example, ExoClick’s {conversions_tracking} and BeMob’s click ID both become external_click_id inside Redsoft.
Platform token→Redsoft value→Destination parameter
Available postback placeholders
Affiliates use these controlled names inside saved destination URLs.
| Redsoft placeholder | What Redsoft inserts | Example value | Typical destination use |
|---|---|---|---|
{external_click_id}Required | The click identifier captured from the campaign link | FWf21zg4HNhG32z2gDBL4h | ExoClick tag, BeMob cid |
{event_id} | Unique Redsoft ID for this registration or conversion delivery | REG-501 | Tracker transaction ID / deduplication |
{order_id} | Unique DarkRoseDating payment order ID | ORDER-1001 | Purchase transaction ID |
{event_name} | The Redsoft event that occurred | registration, purchase | Custom tracker event labels |
{payout} | Numeric conversion value, when configured | 19.99 | BeMob/Voluum revenue or payout |
{currency} | Three-letter currency code | EUR | Revenue reporting |
{package_tier} | The purchased DarkRoseDating coin package | package_3 | Separate package conversion goals |
{event_status} | Verified conversion state | approved | Trackers that support conversion status |
ExoClick registration example
1. Incoming campaign URL
→...?cid={conversions_tracking}2. Redsoft stores
→external_click_id = FWf21zg...3. Redsoft calls
...&tag=FWf21zg...