Adding Data
Last updated
Last updated
Once your store is added, you can add users / data to it. Note that we add via a queue-based approach, so the data may take a couple moments to populate.
When creating your store, you will get a store ID and secret. These are to be provided by the API / Zapier when managing data.
IMPORTANT: Keep these values safe and secure. Anyone with the values can update your store.
There are a few ways you can manage your data. Look for the Manage button, and it should show you them.
Method 1: UI
You can directly manage your store in the interface.
Method 2: API
If you want to use the BitBadges API to send hooks / POST requests to, you can do so manually. We refer you to the interface in the developer portal for getting the exact route / body you might need.
Method 3: Zapier
Use the BitBadges Zapier integration to automate workflows for you. Zapier connects to over 7000+ integrations. In this case, your trigger will be the app you want to integrate nad the action will be BitBadges Add User to Dynamic Store.
Typically, you will want to field map data from your trigger (e.g. Eventbrite attendee email) into the BitBadges Store Action step. For documentation on how to do this, see Zapiers documentation.
You may notice that we have a few different identifier fields (email, address, id, username). Leave the ones you don't need blank. Which field you populate should correspond to the store type you have created.
You can also use the Zapier approach to check criteria as well. For example,
Setup a Google Form that users can enter their email (or parse the Gmail from the metadata).
Setup a Zap to trigger upon Google Forms responses.
Check if existing Mailchimp subscriber using email provided via the Mailchimp integration plugin.
Add email to dynamic store if subscribed (note: we only allow claims for verified emails)
If setting up an in-site claim, you can redirect the users to the form via the URL Click plugin, Custom Instructions Plugin, or just in the description as well.
