Follow these steps to integrate your See Tickets dashboard with Innercrowd:
Step 1: Obtain Information from Your Account Manager
To start integrating Innercrowd with See Tickets, contact your See Tickets account manager and tell them you want to integrate with Innercrowd. Please also inform them if you're setting up the integration for CRM, Ambassador Marketing, or both.
Please request all of the following credentials via your account manager at Paylogic:
Paylogic Shop API Key
PaylogicShop API Secret
Paylogic Config API refresh token
Paylogic Reporting API refresh token
CRM - What to expect from your account manager
Our CRM system is fully integrated with your Paylogic dashboard. This unlocks many unique features within the segmentation process, but it also automates adding ticket buyers as contacts within our system. A new ticket buyer will be added as a contact, and a frequent visitor's contact profile will automatically be updated with their most recent ticket purchase.
To make this possible, Paylogic needs to activate the following:
Unarchiving events in the past and connecting them to the integration
Add the sales channels of all upcoming events to the integration
Ambassador Marketing - What to expect from your account manager
For Ambassador Marketing, we need access to all upcoming events to unlock features like creating personal ticket links and automated rewards. To track ambassador sales, your account manager needs to create a voucher group (with or without a discount).
Note: You can enter dates in the time period a voucher group is active. Please align these dates with the start of your event sales until the event day.
Step 2: Insert the Data into Innercrowd
Once you have the required information, go to Innercrowd Dashboard > Integrations and click on Paylogic. Paste the information into the corresponding fields and click Next.
Step 3: Finalize the Integration
Our system will automatically test the integration. If the test is successful, the integration is complete. If not, please re-enter the API Key, Secret, and Refresh Token to ensure the information is correct.
Step 4: Field mapping
Field mapping ensures that ticket buyer data from Paylogic is correctly matched to the corresponding fields in Innercrowd. For every ticket purchase, buyer information is automatically synced, but only if the fields are properly mapped. Some fields are pre-mapped by default (such as First Name, Last Name, and Email).
To manage your fields, go to the overview of your Paylogic integration, click the three dots, then select Manage Fields. From here, you will see a list of pre-determined fields.
Important: Carefully review the default mappings and make sure they are correct and complete. If a field is not mapped, that data will not be synced from Paylogic. We strongly recommend mapping all available fields now, even ones you don't plan to use right away. This saves you time later if you decide to use that data in the future.
How to add a field mapping: Click + Add Mapping at the bottom of the page. A new row will appear with two dropdowns. First, select the Paylogic field on the left, then select the matching Innercrowd field on the right.
How to remove a field mapping: Click the X icon on the right side of the row you want to remove.
Can't find the right Innercrowd field? If the field you need doesn't exist yet in Innercrowd, you can create one directly from the Innercrowd field dropdown by clicking + Create new field.
Once you've reviewed and completed all your mappings, click Save Field Mappings.
Step 5: Manage Your Consents
Consent mapping determines how a ticket buyer's communication preferences from Paylogic are applied in Innercrowd. This is a critical step! If consent is not configured correctly, you may end up contacting people who haven't opted in, or miss out on reaching people who actually want to hear from you.
Before configuring rules, choose which approach fits your situation. You should use one of the following two options.
Option A: Add Consent Based on Contact Field
Use this if your Paylogic checkout includes a consent checkbox (for example, "Yes, I want to receive the newsletter"). This maps each ticket buyer's individual choice to the correct consent status in Innercrowd.
Click + Add field-based rule. A new row appears with four settings:
Paylogic field: Select the consent checkbox field from Paylogic (for example, a "Subscribe to newsletter" checkbox)
Condition: Choose When checked or When unchecked to define when this rule applies
Consent type: Select the communication channel this rule applies to (WhatsApp, Email, Newsletter, or Push)
Consent value: Choose Subscribed or Unsubscribed to set the resulting consent status in Innercrowd
You can add multiple rules to cover different consent fields and channels. For example, you might create one rule for email newsletter consent and another for WhatsApp.
Option B: Add consent to all contacts
Click + Add rule for all contacts. Select the Consent Type (WhatsApp, Email, Newsletter, or Push) and set the value to Subscribed or Unsubscribed. Click Add Rule to confirm. This rule applies to every ticket buyer who is synced from Paylogic, regardless of any checkbox fields.
We strongly recommend using Option A. By respecting each ticket buyer's individual consent preference, you'll see higher open rates and significantly reduce the risk of unsubscribers and spam complaints. Only contact people who actually want to hear from you.
Sync Behavior
At the bottom of the page, you'll find two toggles that control how consent values are handled during synchronization:
Overwrite on Historical Sync: When enabled, a historical sync (importing all past ticket buyers from Paylogic) will overwrite any existing consent values in Innercrowd. We recommend keeping this turned off to prevent overwriting consent changes that contacts have already made in Innercrowd (such as unsubscribing from emails).
Overwrite on Webhook Updates: When enabled, new ticket purchases will update the contact's consent values in Innercrowd. We recommend turning this on. If a contact gives new consent during a future ticket purchase, this ensures their preferences are kept up to date.
Once you've configured your consent rules and sync behavior, click Save consent mappings.
Success! See Tickets is now successfully integrated with Innercrowd.
What’s Next?
After setting up the integration with Paylogic, it’s time to set up & connect WhatsApp with Innercrowd - click here for the article.




