Playbook: Design a sub-ID taxonomy before scaling a forex campaign

Playbook: Design a sub-ID taxonomy before scaling a forex campaign

What it is: A naming scheme for tracker sub parameters so that, when FTDs come back via postback, you can actually tell what worked.

Best for: Affiliates who scaled first and now have a postback feed they can't slice meaningfully.

The taxonomy:
— Reserve fixed sub slots: sub1=source, sub2=campaign, sub3=creative, sub4=lander, sub5=placement/zone. Decide this before launch — you can't retro-tag past clicks.
— Use short, consistent codes, not free text. 'fb' not 'Facebook', 'lp03' not 'landing page v3 final'. Postback reports choke on spaces and inconsistency.
— Keep one slot empty for a runtime variable (e.g. device or hour) you may want later.
— Document the map in a pinned sheet. A taxonomy nobody can read is no taxonomy.
— Validate that every slot actually passes through to the broker postback — test one click end-to-end before scaling.

Pros:
— Turns a raw FTD feed into source/creative/zone-level decisions
— Short codes keep postback reporting clean and joinable

Cons:
— Rigid schemas feel like overhead before volume justifies them
— Changing the scheme mid-campaign fragments historical data

Who should skip this: One-creative, one-source testers — the taxonomy outweighs the campaign.

Verdict: Tag before you scale.