When Scratcher is connected to Apsis One, each participant who submits a form in your game is created or updated as a profile in Apsis One, with their consent state intact. From there you can trigger welcome and nurture flows, build dynamic segments, and personalise communication based on what the participant did in the game.
This guide walks through the full setup: generating the API key in Apsis One, connecting the account in Scratcher, activating the integration on a campaign, mapping your fields, and testing it before you go live.
Before you start, have these ready:
Admin access to your Apsis One account (to generate an API key)
Access to your Scratcher account with a campaign already built (game + form)
The name of the Apsis One section and list/subscription you want participants to land in
In this article
Step 1 — Generate an API key in Apsis One
The connection between the two platforms is authenticated with an API key generated in Apsis One. Generating the key gives you three values you'll paste into Scratcher: the API URL, a Client ID, and a Client secret.
In Apsis One, under Account Settings, generate a new API key.
Note the following three values:
API URL:
https://api.apsis.oneClient ID — shown when the key is generated
Client secret — shown when the key is generated
⚠️ The Client ID and Client secret are only shown once, at the moment the key is generated. Save them somewhere safe before you leave the screen — you cannot retrieve the secret again afterwards and would need to generate a new key.
Step 2 — Connect your Apsis account in Scratcher
Next, add Apsis One as an integration at the account level in Scratcher and authenticate it with the values from Step 1.
Log in to your Scratcher account.
Go to Integrations in the menu.
Select Apsis and choose to add a new account.
Enter the three values from Step 1:
API URL:
https://api.apsis.oneClient ID
Client secret
Click Install integration.
💡 Tip: Once the account is connected here, you can reuse it across campaigns. You still activate and map the integration per campaign (Steps 4–6), but you only enter the API credentials once.
Step 3 — Grant write permission in Apsis One
For Scratcher to create and update profiles, the API needs permission to write to the relevant keyspace in Apsis One — in particular the email keyspace, which is the unique identifier for a profile. If this permission is missing, the test in Step 7 will fail with an error like "write permission is not granted for type … in this keyspace."
In Apsis One, open the attribute settings for the identifier type (e.g. the email keyspace).
Under Allowed operations for identifier type, enable write (and read) for external sources such as API and integrations.
Save.
⚠️ This is the most common cause of a failed first test. The credentials can be correct and the mapping complete, but if the API cannot write to the email keyspace, no profile is created. Set this before testing.
Step 4 — Activate the integration on a campaign
The integration is switched on per campaign. Open the campaign you want to connect and add Apsis One to it.
Go to Manage campaigns in the left-hand menu.
Find the campaign you want to connect and click the pen (edit) icon on that campaign's row.
In the campaign editor, open Connect (bottom-left).
Click Integrations.
Click the Apsis integration tile.
Step 5 — Choose account, section and map your fields
This is where you decide where the data lands in Apsis One and which Scratcher fields fill which Apsis attributes. The mapping determines how much of your automation can actually trigger, so scope it carefully.
Select account — choose the Apsis One account you want to create the profiles in (e.g. Production).
Apsis Section — choose the correct section; profiles and attributes live inside a section's data model.
Field mappings — map each Scratcher form field to its destination Apsis attribute. Use Add Field Mapping to add more rows.
The integration uses the Email keyspace, so email is always mapped. It's the unique identifier for a profile in Apsis One — every participant needs an email for their data to be stored and matched.
Always map, at minimum:
Any profile / preference fields the game collects that your segments or flows rely on
Campaign ID and Campaign Name, if you want to segment or report by campaign from attributes.
You can optionally use Filter by permissions to only send leads who accepted specific permissions. Leave it empty to send all leads.
Step 6 — Set the subscription (consent)
Data is captured with consent in exchange for the prize, and that consent is written to Apsis One with the profile. Choosing the right subscription is what adds the consent to the profile — and what your marketing automation flows key off.
Under Subscriptions (consents), choose the subscription the participant should be opted into.
Leave it empty only if you deliberately do not want to add a consent.
Click Save. You should see "Integration updated successfully."
⚠️ The subscription you pick here must match the entry condition of the flow you want to trigger. If the flow listens for a different subscription, profiles will sync correctly but the automation won't fire.
Step 7 — Test the integration
Before going live, run a test to confirm data actually reaches Apsis One.
In the Apsis integration panel, click Test.
Fill in the test fields:
Select list — the target list
Email — a test email address
Campaign ID — found in the URL of the campaign
Campaign Name and Prize Name, if mapped
Click Send test.
Confirm the test profile appears in Apsis One in the expected section and list, with the consent applied.
💡 Where's the Campaign ID?
It's in the campaign's URL. Copy it from there when running the test.
If the test returns "write permission is not granted for type … in this keyspace," go back to Step 3 and grant write permission to the email keyspace, then test again.
Step 8 — Go live
Once the test profile lands correctly in Apsis One with consent applied:
Make sure the integration is saved on the campaign.
Confirm the campaign's live date/time (and time zone).
Publish the campaign.
From go-live, every participant who completes the form syncs to Apsis One continuously — created if new, updated if they already exist — ready for your flows and segments to act on.
Troubleshooting
Work top-down: confirm each stage before moving to the next, so you isolate the break instead of guessing. Most issues sit at the hand-off between the game submission and the write-back to Apsis One.
1. Reproduce with a test submission. Open the live URL, complete the full journey, and submit a test form. Check it appears in the Scratcher dashboard first — if not, the problem is upstream of Apsis.
2. Verify the integration is connected. Confirm Apsis is added at the right level and still authenticated. A silent re-authentication is a common cause.
3. Check the field mapping. Every required Scratcher field must map to an Apsis field, including email and the consent field. Unmapped means incomplete or missing data.
4. Confirm the target list / section. Make sure the integration points at the list your flow and reporting actually use — not a leftover test list.
5. Trace consent → flow → segment. Check the profile's permission state, that the flow's entry condition matches the subscription, and that dynamic segment rules read the mapped fields.
Still stuck? When contacting support, include: the campaign URL, the test profile's email, the timestamp of the test submission, a screenshot of the field mapping, and which list/section is targeted — plus what expected result is missing.
What's next?
Build a welcome or nurture marketing automation flow in Apsis One that triggers on the subscription you mapped in Step 6.
Create dynamic segments that read the profile attributes your game collects, so you can branch and personalise follow-up.
Set up a reactivation or loyalty campaign that reuses the connected account across multiple Scratcher games.