Connect this destination to export audience membership as a Community tag, for use in Community campaigns.

This destination writes to your Community account and is a good fit when you want to:

Send phone number, date of birth, and state
Make GrowthLoop audiences available for SMS engagement

This maps to GrowthLoop Audiences and Journeys:

Use it for	Audiences	Journeys
Sending GrowthLoop audiences to Community SMS tags	✓	✓

Prerequisites

Make sure you have:

A Community account. If you do not have one, book a demo.
Your Client ID and an Auth Token from API Tokens in Community.

Set up Community as a destination

In GrowthLoop, click the Destinations tab on the left sidebar.
Click New Destination in the top right corner.
Search for Community and click Add Community.

Enter the required information, then click Create.

Field	Description
Destination Name	Name this destination in GrowthLoop. Use a name so your team recognizes its purpose, like "Community SMS".
Sync Frequency	Set the default export frequency (for example, daily or weekly). You can override this setting for individual exports.
Client ID	Unique identifier from Community Settings → API Tokens.
Auth Token	Token you've created on the same API Tokens page.

GrowthLoop validates the connection. Community then appears in your list of connected destinations.

Export to Community

From within GrowthLoop, export from an audience or from a journey Destination Node. See Export an audience or Build a journey if you need more information on these steps.

After building or selecting an audience, click Export, then search for Community.

In a journey, add a Destination Node under SMS and select Community.

Map contact identifiers

Map the required fields. Optional fields can improve targeting in Community.

Match field	Required	Format
Phone	Yes	`XXX-XXX-XXXX`
Date of Birth	Yes	`YYYY-MM-DD`
State	Yes	Full name or abbreviation, for example `California` or `CA`
Given name / Surname	No	Name fields
City / Country / Postal	No	Address fields
Gender	No	Gender value
Latitude / Longitude	No	Location fields

You can also map custom attributes from the audience or from the journey as additional fields.

Configure the export

This is where you set the campaign type and schedule for audience exports. On a journey Destination Node, you set timing on the journey canvas.

Setting	Audience export	Journey Destination Node
Export Name	Defaults to the audience name.	Required. Enter a name so you can find the export in GrowthLoop and Community.
Campaign type	Choose a one-time or ongoing export.	The journey schedule controls when the journey runs and contacts are sent to Community.
Schedule	Set frequency, start date, end date, and days of the week.	Users reach this node when the journey runs. Add a Delay Node or set Criteria Evaluation to control timing.

Export behavior

This is what GrowthLoop writes when you export an audience.

Behavior	What happens
What GrowthLoop writes	A tag in Community with matching members. Direction is GrowthLoop → Community.
When it runs	GrowthLoop sends the export as a batch on the next successful run. An export that starts Now runs within about 15 minutes. Journeys send exports on demand when users reach the Destination Node.
Delivery	GrowthLoop creates a tag in Community and loads matching members.
Required fields	Phone, date of birth, and state must be mapped.
Personalization	Additional fields are supported.
One-time exports	GrowthLoop sends current membership once.
Ongoing exports	GrowthLoop sends updated membership on each scheduled run.

Confirm the export was successful

When the run finishes, confirm you can use the data in Community.

Audience export: Open Communities and look up the tagged community named after the export.
Journey Destination Node: Open Communities and look up the tagged community named after the export. Confirm a contact who reached the node is in it.

In GrowthLoop, review counts on the audience Exports tab, or open the Activity tab on the journey Destination Node. See Export an audience or Monitor a journey for more information.

Congrats on successfully exporting to Community!

Troubleshooting

These are the issues we see most often. You can always email us at [email protected] for help.

Problem	Cause	Resolution
Connection fails to validate	The values are your Community login, not API tokens	Copy Client ID and Auth Token from Community API Tokens
Rows fail to load	Phone, date of birth, or state is missing or in the wrong format	Map Phone, Date of Birth, and State in the formats above
The tag is missing	Community has not finished importing the export	Refresh Communities after the export finishes