Surfaces
Affiliates Tracking
Campaign tracking, UTM presets, reward tables, affiliate codes, discounts, and active states.
First created Last updated
Overview
Affiliates Tracking connects marketing links, attendee discounts, referral attribution, and reward rules. It is used when the event wants to understand which campaigns drove registrations or when affiliates should receive a tracked reward.
Dashboard route
/ems/manage/affiliates-tracking?id=:eventId
Feature settings
| Input or control | What it changes | Before saving |
|---|---|---|
| Enable affiliates and tracking | Allows attendee rego to capture affiliate attribution, campaign UTM data, and linked affiliate discounts. | Confirm the event has a tracking policy before turning on. |
| Affiliate cookie lifetime (days) | Sets how long attribution persists after someone opens an affiliate link. Accepts 1-365 days. | Default is 7 days. Match the campaign promise and privacy expectations. |
| Feature badges | Show whether campaigns, reward tables, and affiliates are active for the event. | Disabled badges mean records may exist but tracking is not enabled. |
| Floating save bar | Saves settings, campaigns, reward tables, and affiliates; or reverts all to the last loaded state. | Revert if a campaign code, reward rule, or affiliate code was changed by mistake. |
Campaign controls
| Input or control | What it changes | Before saving |
|---|---|---|
| Add campaign | Creates a campaign record. | Use one campaign per channel or initiative. |
| Campaign title | Staff-visible campaign name. | Required. Use a name that finance and marketing can recognize. |
| Campaign code | Stable code used in campaign links and UTM defaults. | Required and must be unique among campaigns. |
| Landing path | Optional attendee-facing path the campaign link opens. | Leave blank to use the default public event page. |
| UTM source | Identifies who or what sent traffic. | Examples: instagram, newsletter, creator-collab. |
| UTM medium | Identifies the channel type. | Examples: affiliate, social, email, qr. |
| UTM campaign | Identifies the overall promotion. | Usually matches the campaign code. |
| UTM content | Optional creative, placement, or variant label. | Examples: story-set-01, hero-banner, bio-link. |
| UTM term | Optional keyword, audience segment, or batch label. | Use only when reporting needs the extra dimension. |
| Notes | Internal campaign context. | Record owner, launch dates, or where the link will be posted. |
| Active | Makes the campaign usable for share links. | Inactivate old campaigns instead of deleting audit context. |
| Campaign share link | Generated link targeting the attendee-facing rego site. | Save the event slug first if the link cannot be generated. |
Reward table controls
| Input or control | What it changes | What each option means |
|---|---|---|
| Add reward table | Creates a reusable reward setup that affiliates can link to. | Use one table for each reward policy. |
| Table title | Required name for the reward table. | Titles must be unique. |
| Reward system | Chooses automatic reward behavior. | No automatic reward tracks only. Conversion milestones unlocks rewards at thresholds. Commission payout calculates commission and collects payout method choices. |
| Reward label | Categorizes the reward. | Kickback, Merch, Service, or Other. Use the label that matches the published affiliate terms. |
| Reward details | Optional description of the reward. | Use attendee/affiliate-facing wording where appropriate. |
| Active | Enables the reward table for use. | Keep inactive until finance or marketing approves it. |
| Notes | Internal reward-table context. | Record owner, agreement, or settlement notes. |
Conversion reward settings
| Input or control | What it changes | Before saving |
|---|---|---|
| Progress mode | Chooses how conversion progress is measured. | Sales amount uses currency thresholds. Custom points uses points from sales-per-point or item rules. |
| Sales amount per point | Converts sales totals into points when Progress mode is Custom points. | Required if points mode has no per-item point rules. |
| Add target | Adds a milestone. | Conversion reward tables need at least one milestone. |
| Milestone threshold | Sales amount or point count required to unlock the milestone. | Match the selected progress mode. |
| Milestone title | Name of the unlocked reward. | Keep it understandable in emails or toasts. |
| Milestone reward label | Categorizes that specific milestone. | Kickback, Merch, Service, or Other. |
| Milestone reward details | Adds details for that milestone. | Explain what the affiliate receives. |
| Milestone description | Adds a longer description. | Use for fulfillment or qualification notes. |
| Add rule | Adds a per-item point rule. | Use when some tiers or add-ons should count more than others. |
| Item type | Chooses the item source for a point rule. | Rego tier uses tier options. Add-on uses add-on options. |
| Item | Selects the specific tier or add-on. | If no items are available, configure Rego Config first. |
| Points | Points awarded for that item. | Must be above zero to be retained. |
Commission reward settings
| Input or control | What it changes | Before saving |
|---|---|---|
| Commission percent | Percentage used to calculate affiliate commission. | Required and must be greater than zero for commission reward tables. |
| Allowed payout methods | Checkboxes generated from event payment providers. | At least one payout method is required for commission reward tables. |
| No payout methods available | The event has no payment providers to offer as payout methods. | Add providers in Payments Config before enabling commission rewards. |
Affiliate controls
| Input or control | What it changes | Before saving |
|---|---|---|
| Add affiliate | Creates a username-linked affiliate record. | Confirm the user identity and agreement before creating the record. |
| Username | Connects the affiliate to an account. | Enter without @; every affiliate needs a username. |
| Tracking code | Code used in affiliate links and attribution. | Required and must be unique. |
| Attendee discount type | Chooses affiliate discount calculation. | Flat amount subtracts a fixed PHP amount. Percent subtracts a percentage and cannot exceed 100%. |
| Attendee discount value | Optional discount given to attendees using the affiliate link. | Leave blank for tracking-only affiliates. |
| Reward table | Links one reusable reward table. | No automatic reward means attribution is tracked without reward automation. |
| Notes | Internal affiliate context. | Record agreement terms, owner, or payout follow-up. |
| Active | Makes the affiliate code usable. | Activate only after reward and discount settings are reviewed. |
| Applies to gifted regos | Allows this affiliate code to discount and attribute the gifter’s gift purchase flow. | Leave off unless the affiliate agreement covers gifted rego purchases. |
| Applies to shop orders | Allows this affiliate code to discount and attribute Event Shop carts. | Leave off unless the affiliate agreement covers merch/shop purchases and any reward table should count shop conversion value. |
| Affiliate share link | Generated direct affiliate link. | Check the code and destination before giving it to the affiliate. |
| Campaign-specific share links | Generated links combining active campaigns with the affiliate code. | Use when a creator is sharing a specific campaign. |
| Payout setup display | Shows payout method/account details supplied by the attendee for commission rewards. | Review before settlement and do not share outside authorized finance staff. |
Affiliate applicability is checkout-specific. Registration attribution, gifted rego attribution, and shop-order attribution may have different campaign agreements, reward tables, discount promises, and finance reporting effects. Confirm the agreement before enabling a code outside regular rego.
Validation and generated states
| State or validation | Meaning | What to do |
|---|---|---|
| Duplicate campaign code | Two campaigns use the same code. | Rename one before saving. |
| Duplicate reward table title | Reward table titles conflict. | Use distinct policy names. |
| Conversion table needs milestones | A conversion reward table has no targets. | Add at least one target. |
| Points mode needs point rules or sales-to-point conversion | Points mode has no way to calculate progress. | Add sales amount per point or per-item rules. |
| Commission table needs payout methods | Commission rewards have no allowed payout method. | Select at least one provider from event payment providers. |
| Duplicate affiliate tracking code | Two affiliates use the same code. | Rename one before saving. |
Flowchart context
Create an Event links here during marketing setup after coupons. Finance closeout may review affiliate results when rewards or commissions need settlement.
Common mistakes
Do not create affiliate discounts without a reward policy. Staff need to know whether the code is for tracking only, attendee discount, affiliate reward, gifted rego attribution, shop order attribution, or all of those.
Configuration saves return the durable primary result without waiting for analytics hydration, notification fan-out, or a full registration-mirror rebuild. Those secondary effects run as bounded background work. Do not repeatedly press Save because an analytics count has not refreshed yet; refresh the page once after the success state if a current report is required. If a side effect fails, use its operational log or retry path rather than rewriting the affiliate configuration.