Skip to main content

How to connect to Moshtix

Steps to connecting your Moshtix account to Audience Republic

Support Team avatar
Written by Support Team
Updated yesterday

Article Navigation

Moshtix: determining your event ownership

Direct Event Ownership:
If you are the primary owner of all the events in your Moshtix account, using the Moshtix API key is the best option.

Shared Events:
If the events in your Moshtix account are shared with you by venues or other promoters, the “Shared With Me” report would be the recommended integration method.


Direct event ownership:

Automatically sync your past, current and future events, ticket sales and attendees every hour with the Moshtix Integration.

  • Sync all of your previous and upcoming Moshtix events, ticket sales and customers

  • Sync Moshtix segments to Message lists or Facebook Custom Audiences

  • Clients and Moshtix administrators can create new keys directly from the Moshtix control room. API keys are used to retrieve data and perform actions in your Moshtix client account.


Connect Moshtix to Audience Republic

  • From your Account (bottom left) select Account Settings

  • Choose the Integrations tab

  • Click Connect Moshtix

  • Subscribe associated contacts to list: We recommend creating a new list for the opt-ins to sync to

  • Enter one of the following: your access token OR your username and password

  • Click Confirm

Head over to the Events menu to see your past and future Moshtix events. Please note that it may take a few minutes to fully sync your past attendee data.


How to pull API tokens from Moshtix

Clients and Moshtix Administrators can create new keys directly from the Moshtix control room. API keys are used to retrieve data and perform actions in your Moshtix client account.

1) Log into the Moshtix Control Room HERE

2) Under 'Account' click 'API Keys'

If you cannot see this option, contact your Moshtix client account manager by selecting 'Get Help' in the bottom left of your Moshix account.

3) Click 'Add Key' and enter a name for your new API key*

Add API Key.png

*This name should be unique and easily identifiable, You may want to name the Key after the app or service you will be using with the Moshtix API.

4) Click 'Create Key'

5) The Key is generated and can be copied directly to the clipboard to be pasted into the API set-up on the external platform / app.


Connect additional Moshtix accounts

  • You can also connect more than one Moshtix account to your Audience Republic account.

  • Simply click on the drop-down menu > Add New Account


What data will be synced?

  • Event data: name, date, ID, time

  • Ticket/order data: price, ID, purchase time, process refund data

  • Contact data: Full name, email address, Mobile number with country code, city, state, date of birth, gender

  • Auto sync frequency is instant

  • Historical sync limit is 24 months


What data won't be synced?

  • Event images

  • Processed refund data

  • Country

  • Tags

  • Webhook syncs


Joint event ownership

Before you get started, please ensure you have an active Moshtix account with reporting access. Your Audience Republic Customer Success Manager will need to provide you with:

  • Optional Path (this should be your Promoter OID)

  • Access Key

  • Secret Key


How to set up the Moshtix Shared With Me Report

  • Navigate to Reports > Insights > Shared with me

    • Select "Purchases by Ticket"

  • Configure two reports: one for historical data (Send) and one for ongoing data (Schedule)

  • Click on the 'Actions' gear and select 'Schedule'

  • Set up your schedule

    • Name your schedule

    • Select ‘Amazon S3’ as the report destination

    • Enter the AWS credentials and bucket details:

      • Bucket: ar-integrations-moshtix

      • Optional Path: use credentials provided by Audience Republic (your OID)

      • Access Key and Secret Key: use credentials provided by Audience Republic

      • Region: Asia Pacific (Sydney) - ap-southeast-2

  • Set the file format to CSV

  • Configure the filters

    • Booking Transaction Timestamp Time: "in the past 2 days"

    • Client (For Event) Shared Client: select ‘any value’

    • "Event is not null" ensures that all ticket orders are attached to a valid event

    • "Orders Subscribed To" Event Organiser - is any value

  • Under ‘Advanced Options', ensure the Limit ‘All Results’ is selected, otherwise, exports are limited to 5,000 rows by default.

Click Save All, then reopen the report and click Send Test

Once the credentials have been added, please notify your customer success manager or customer support, as the Audience Republic team will need to complete one final step.


Exporting historical data

  • You may also wish to do a historical export. To do this, open the ‘Send’ menu item from the action gear. Fill out the form as per the scheduled report (obviously, there is no scheduled in this version of the form).

  • The only difference should be the Booking Transaction Timestamp Time, which you can configure as per the customer’s historical data needs.

  • After pressing ‘Send’, keep an eye on the S3 bucket to ensure the data arrives.


What data will be synced?

  • Contact ID, name, email address, mobile number,

  • Date of birth and gender,

  • State, postcode and city

  • Event name, ID and event time,

  • Event images aren't included in Moshtix exports

  • Sync Tickets/Orders

  • Ticket price

  • Only contacts that have ordered something are synced

  • Auto sync frequency is Daily

  • Historical time limit is 24 months

  • Marketing Opt in available from provider


What data won't be synced?

  • Country

  • Tags

  • Webhook syncs

  • Event images


Data Discrepancy

Please note there may be a 3-5% data discrepancy with our ticketing integrations. For Moshtix, 60% of orders will be synced. This is a normal occurrence as we are a data aggregator and each ticketing platform has its unique way of calculating and displaying ticketing data. Therefore, when such data is displayed in Audience Republic, a certain percentage of difference is to be expected.

Did this answer your question?