Segment Integrations

Segment is the data pipeline that collects activity from PodPlay (such as Customer sign-ups, reservations, and event activity) and forwards it to your marketing and analytics tools. The Segment section is where you connect a venue's data sources to PodPlay, then turn on destinations like Mailchimp, Google Tag Manager, and Facebook Pixel. Use this when a Club is setting up marketing tracking or email automation for the first time, or when you need to update an existing connection.

PLEASE NOTE: The Segment section is only visible to PodPlay administrators. Front desk staff and Club managers will not see it. If a Club asks for a Segment-powered integration, the PodPlay team completes the setup here.

Where to find the Segment settings

• Open Company Settings for the venue you manage
• Click the Integrations tab
• Scroll to the Segment section

[SCREENSHOT NEEDED: Integrations tab in Company Settings with the Segment section visible]

Each action in this section is saved on its own — there is no shared Save Changes button for Segment. When you create or update something, the change is applied immediately and a confirmation message appears.

Set up the data sources

Sources are how PodPlay sends data into Segment. A venue can have two:

• Web Source — activity from the website and customer app
• Backend Source — activity from PodPlay's servers

Destinations cannot be added until the matching source exists, so set up the sources first.

Create new sources

• If no sources exist yet, click Create Sources to set up both the Web and Backend sources at once
• If only one source is missing, use Create Web Source or Create Backend Source to add just that one

When a source is created, PodPlay automatically configures its write keys and links it to Segment.

[SCREENSHOT NEEDED: Segment section showing the Create Sources button before any sources exist]

Find sources that already exist

If a write key is already saved but the source is not yet linked, a Find Existing Sources button appears.

• Click Find Existing Sources to match the saved write key to a source in Segment
• If a match is found, the source is linked automatically and its name appears with a link to the Segment dashboard

If the source cannot be matched by its write key, a message appears asking for the Source ID instead:

• Copy the Source ID from the Segment dashboard
• Paste it into the Web Source ID (or Backend Source ID) field
• Click Link Web Source by ID (or Link Backend Source by ID)

[SCREENSHOT NEEDED: The "Couldn't match" message with the Source ID field and Link button]

Edit the backend write key

When a Backend Source is connected, you can update its write key directly from the Backend Source row using the edit (pencil) control.

Connect a Facebook Pixel

The Facebook Pixel sends Customer activity to Facebook for ad tracking. It runs in the customer's browser, so it only needs the Web Source. The Facebook Pixel section appears once the Web Source exists.

Create the Facebook Pixel destination

• In the Facebook Pixel Integration section, enter the Pixel ID in the field
• Click Create Facebook Pixel Destination

When created, a green Facebook Pixel destination configured confirmation appears with the Pixel ID shown below it.

[SCREENSHOT NEEDED: Facebook Pixel Integration section with the Pixel ID field and Create button]

Update the Pixel ID

• Click Edit Pixel ID
• Enter the new Pixel ID
• Click Update Facebook Pixel Destination, or click Cancel to discard the change

[SCREENSHOT NEEDED: Facebook Pixel Integration section in edit mode showing Update and Cancel buttons]

Connect Google Tag Manager

Google Tag Manager (GTM) lets a Club manage its own marketing and analytics tags. Like the Facebook Pixel, it runs in the customer's browser and only needs the Web Source, so the section appears once the Web Source exists.

Create the Google Tag Manager destination

• In the Google Tag Manager Integration section, enter the Container ID (it looks like GTM-XXXXXX)
• Click Create GTM Destination

A green Google Tag Manager destination configured confirmation appears with the Container ID shown below it.

[SCREENSHOT NEEDED: Google Tag Manager Integration section with the Container ID field and Create button]

Update the Container ID

• Click Edit Container ID
• Enter the new Container ID
• Click Update GTM Destination, or click Cancel to discard the change

Connect Mailchimp

Mailchimp powers a Club's email marketing. Because it sends both website and server-side activity, the Mailchimp section only appears once both the Web Source and Backend Source exist.

Create the Mailchimp destinations

Gather these three values from the Club's Mailchimp account first:

• Mailchimp API Key
• Audience ID
• Datacenter ID (for example, us6)

Then:

• Enter all three values in the Mailchimp Integration section
• Click Create Mailchimp Destinations

When created, a green Mailchimp destinations configured confirmation appears showing the Audience, Datacenter, and a masked preview of the API Key.

[SCREENSHOT NEEDED: Mailchimp Integration section with the API Key, Audience ID, and Datacenter ID fields]

Update the Mailchimp credentials

• Click Edit credentials
• Update any of the three values

  • Leave the API Key blank to keep the current key
• Click Update Mailchimp Destinations, or click Cancel to discard the change

[SCREENSHOT NEEDED: Mailchimp Integration section in edit mode showing Update and Cancel buttons]

Tips

• Always create the sources before trying to add a destination — the destination sections stay hidden until the required source exists.
• The Facebook Pixel and Google Tag Manager sections need only the Web Source; Mailchimp needs both sources.
• Each integration saves on its own when you click its Create or Update button — there is no shared save step.
• If the Segment section fails to load, click Retry to try loading it again.
• If a source can't be matched by its write key, link it directly with the Source ID from the Segment dashboard.