DarkRoseDating marketing
Campaigns & campaign links
Create a campaign, add its MTL and VTL links, then attach tracking once for the whole campaign.
One assigned tracking configuration can cover every campaign link
Every MTL and VTL link below uses the same saved click-ID mapping and event destinations.
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
Assigned tracking configuration
This campaign is assigned the ExoClick configuration below. Its saved event destinations apply to every campaign link.
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 the click and assigned configuration → registration or purchase fires that configuration’s matching event destination.
Marketing
Postback configurations
Manage the event destinations attached to each DarkRoseDating campaign.
The assigned tracking configuration selects the destination
The click ID identifies the external click. The assigned configuration tells Redsoft which registration or purchase destination to call. Campaign names are labels only.
Campaign link→Assigned configuration→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...Developer handover
Suggested implementation guide
One possible way to build the concept shown in this prototype.
The developers could adapt the data model, naming, queues, and frontend integration to Redsoft’s existing architecture. The important part is preserving the relationships and verified-event flow.
Campaign + links→Assigned configuration→Stored attribution→Verified event→Correct destination
1Separate campaigns from tracking configurationsWhat these two records mean and why they are separate
A campaign could contain the business-facing information: its name, country and links. A tracking configuration could contain the technical information: which URL parameter carries the click ID and which destinations receive registration or purchase events.
In normal languageThe campaign is the folder. The tracking configuration is the set of delivery instructions assigned to that folder. Naming the campaign “ExoClick” does not make it an ExoClick integration—the assigned configuration does.
campaigncampaign_linktracking_configurationevent_mappingclick_attribution2Create a campaign and its linksWhat campaign ID, link ID, destination and model selection mean
The affiliate could create one campaign and place several MTL or VTL links inside it. This can support the wider link business, not only tracking.
- Campaign ID
- Redsoft’s internal identifier for the group of links.
- Link ID
- Identifies the exact MTL or VTL link the visitor used.
- Destination URL
- The DarkRoseDating page the link opens.
- Model/landing selection
- Your existing
srcm=ggorsrcm=lilithbehavior. It selects the model experience and is not required for S2S itself.
Possible resultOnce a configuration is assigned, Redsoft could add its incoming click parameter to every generated link automatically.
3Capture the incoming click IDHow differently named platform parameters become one Redsoft field
Redsoft does not automatically recognize every platform. The affiliate or a preset must state which URL parameter contains the click ID.
ExoClick: exo_click → external_click_idBeMob: cid → external_click_idCustom tracker: subid → external_click_idIn normal language“Standardize” only means Redsoft reads the configured parameter and saves its value under Redsoft’s consistent internal field name,
external_click_id.4Remember the attribution and assigned configurationWhat the external identifier is and why Redsoft does not need to guess
The external identifier is the real click ID received from ExoClick, BeMob or another platform. Redsoft could save it together with the exact tracking configuration that was assigned when the visitor arrived.
Possible saved record
external_click_id = ABC123 · tracking_configuration_id = CONFIG-EXO-1Why this mattersWhen the visitor later purchases, Redsoft follows
CONFIG-EXO-1. It never tries to identify the platform by looking at the letters inside ABC123.5Use verified Redsoft eventsThe central trigger that everything else depends on
This is the bread and butter of the system. Redsoft first confirms what actually happened, such as a completed registration or successful Package 2 payment.
registration_completedpurchase_completedpackage_1_purchasedpackage_2_purchasedFor the developersConnect these verified business events to the tracking module. Do not trigger purchases from a package-button click or an unconfirmed page load.
6Deliver a Custom S2S eventHow this replaces the current one-off custom-code approach
This is essentially the process your current custom script performs: read the saved click ID, detect the conversion, build the postback URL and send it. The proposed module makes that process reusable across campaigns and destinations.
Possible flow
verified event → load assigned mapping → replace Redsoft placeholders → validate URL → send GET/POST → save resultWhat it replacesIt replaces separate handwritten tracking code for every campaign. It does not replace ExoClick, BeMob or the external tracker.
7Trigger a Google Ads browser eventHow several package conversions can work on the same page
The main Google tag could load once. Each Redsoft event could be mapped to its own Google send_to value. After Redsoft confirms the result, browser application code runs only the matching conversion command.
Possible browser flow
Package 2 confirmed → select Package 2 send_to → run one gtag conversion with order ID, value and currencyImportantThe conversion snippets should not all execute automatically in the header. The developers must connect the confirmed Redsoft result to the correct browser event. The exact connection method depends on the existing application.
8Handle missing IDs and prevent duplicatesWhat an idempotency key means
Redsoft should still record its internal registration or purchase when no external click ID exists, but it should skip the external delivery instead of inventing an ID.
Idempotency keyA unique delivery key—such as
CONFIG-EXO-1 + purchase + ORDER-1001—that lets Redsoft check whether this exact conversion was already sent. Reloads and retries therefore cannot report the same purchase twice.retry temporary errorsskip duplicatesdo not invent click IDssave response status9Test before enablingA possible safe rollout
The dashboard could validate required placeholders and show a completed example URL before the configuration becomes active.
Suggested rollout
validate template → preview completed URL → test response → enable one campaign → review results → expandPossible first releaseBegin with Custom S2S and Google browser events. Google server-side conversion uploads could remain a separate later integration.