Your First Campaign, Zone & Test Conversions

1. Go to affset.com and click Start free.
2. Enter a namespace (e.g. acmedemo) and your email.
3. Open the one-click sign-in link from your inbox (it also verifies your address).
4. You land on the dashboard with a Get started card — that card is Step 1.
5. You can request a fresh link anytime from https://{namespace}.affset.com/login.
6. If you need the REST API later, create an API key inside the dashboard.

Tip: Signing in is email-only — nothing to copy or store at registration.

1. On the dashboard’s Get started card, click Set up solo under Just me.
2. Affset creates two profiles on your own email — you+advertiser@… and you+publisher@… — and the card switches to Create campaign. Nothing is emailed; they are simply your identities in the campaign and zone forms.
3. That is the whole setup. Both forms preselect these profiles, so you never pick a role again.

Tip: Solo profiles count as team seats — on Free that is you plus both profiles, 3 of 3. Revoke one on Team if you later need the seat.

1. Click Create campaign on the Get started card (or Campaigns → Create campaign).
2. Advertiser is already filled with your solo profile. On the team path, pick advertiser@example.com.
3. Fill in the demo values below and save.
4. New campaigns start paused — go back to the campaigns list and start your campaign.

Tip: Keep the {click_id} macro in the redirect URL. Affset replaces it on every click.

1. Sidebar → Zones → New zone.
2. Publisher is already filled with your solo profile. On the team path, pick publisher@example.com.
3. Fill in the demo values below and save.
4. On the new zone, click Get zone URL and copy the serve URL.
5. Paste the zone UUID into the workspace panel on this page.

Tip: The zone ID is a UUID. The serve URL uses api.affset.com — copy it from Get zone URL in the dashboard.

1. Open your serve URL in a browser (or send traffic to it).
2. Affset records an impression for the zone.
3. It picks your Demo Offer campaign and redirects to the postback demo with click_id filled in.
4. That redirect records a click.
5. On the postback demo, confirm Detected parameters shows the real click_id.

Tip: source_click_id is your tracking label (the traffic source’s click id). Affset carries it from click through to the conversion callback. Legacy sub_id still works as an alias.

1. Open the affiliate attribution demo in a second tab — its request log will show the publisher callback.
2. Return to the postback demo and click Complete purchase.
3. Confirm the technical log shows a successful request to https://api.affset.com/px/{click_id}.
4. Return to the affiliate attribution demo and click Refresh timeline.
5. You should see source_click_id and payout in the new callback entry.
6. Open Sidebar → Conversions in the dashboard to see the attributed conversion record.

1. Sidebar → Statistics.
2. Confirm impressions ≥ 1, clicks ≥ 1, conversions = 1, payout/spend = 2.00.
3. Open Sidebar → Conversions to see the individual conversion record (click_id, payout, conversion type).
4. Try Group by → source_click_id to see your traffic label, or conversion_type to see subscription.
5. Repeat Steps 4–5 with different source_click_id values to make the demo feel alive.

Tip: Statistics update within a minute. Conversions lists each attributed event — useful for debugging the full funnel.