[{"_1":2,"_1943":-5,"_1944":-5},"loaderData",{"_3":4,"_1925":1926},"root",{"_5":6,"_7":8,"_15":16,"_23":24,"_88":-5,"_89":90,"_124":125,"_1760":1761,"_1762":1763,"_1917":1918,"_1919":1920,"_1921":1922,"_1923":-5,"_1924":71},"cspNonce","8022952ee325587f6108b7eb41f0abe8e5291fc36a62dad19138e543f74c8694","firebaseConfig",{"_9":10,"_11":12,"_13":14},"apiKey","AIzaSyDCG_xdkCxQ0mNJT1LKg2XIf0cHJwSISYU","authDomain","help.growthloop.unthread.io","projectId","unthread","session",{"_17":18,"_21":22},"user",{"_19":20,"_21":22},"uid","anon_1771460488527_2yiu4ih","anonymous",true,"portal",{"_25":26,"_27":28,"_29":22,"_30":22,"_31":-5,"_32":-5,"_33":-5,"_34":35,"_37":38,"_46":47,"_48":49,"_57":58,"_59":60,"_63":64,"_69":-5,"_70":71,"_72":71,"_73":74},"id","2262f98b-42a9-45d1-82f4-ef19b1c85260","tenantId","u-growthloop-s7j0t","isExternal","isEnabled","customDomain","signInEmailSender","previewUrl","projectIds",[36],"f6af0f7d-6e26-4e72-9367-33cc21a55621","customLinks",[39],{"_40":41,"_42":43,"_44":45},"title","GrowthLoop Docs","link","docs.growthloop.com","icon","link-outline","featuredCollections",[],"settings",{"_50":51,"_52":53,"_54":55,"_56":22},"logoUrl","https://firebasestorage.googleapis.com/v0/b/trnout-co.appspot.com/o/u-growthloop-s7j0t%2Fslack%2F0a8010fc-a08c-424f-883a-1354b4cd7ff7-upload.png?alt=media","primaryColor","#1653f1","darkThemeAccentColor","#ffffff","allowDirectTicketCreation","identityPlatformTenantId","e-growthloop-paj4r","homepageMetadata",{"_40":61,"_62":61},"","description","loginMethods",[65],{"_66":67,"_68":22},"type","magicLink","enabled","statusBanner","requireAuthentication",false,"restrictLoginToAccountDomains","tenant",{"_25":28,"_75":76,"_77":78,"_81":82},"name","GrowthLoop","allowedEmailDomains",[79,80],"growthloop.com","flywheelsoftware.com","allowedPriorities",{"_83":71,"_84":22,"_85":22,"_86":22,"_87":22},"1","3","5","7","9","userProfile","projects",[91],{"_75":92,"_93":-5,"_94":-5,"_62":61,"_95":96,"_119":-5,"_120":121,"_122":123,"_25":36,"_27":28},"GrowthLoop External","supportName","supportLogo","workingHours",{"_68":22,"_97":98,"_99":100,"_101":102},"holidays",[],"timezone","US/Pacific","intervals",[103,107,110,113,116],{"_104":105,"_83":106},"0",540,1080,{"_104":108,"_83":109},1980,2520,{"_104":111,"_83":112},3420,3960,{"_104":114,"_83":115},4860,5400,{"_104":117,"_83":118},6300,6840,"defaultTriageChannelId","createdAt","2024-11-05T01:00:57.810Z","updatedAt","2025-10-23T17:54:47.128Z","articles",[126,143,151,158,167,176,185,194,203,212,221,230,239,248,257,266,275,284,293,302,311,320,329,338,347,356,365,375,384,393,402,411,420,429,438,447,456,465,474,483,492,501,510,519,528,537,546,555,564,573,582,591,600,608,617,626,635,644,653,662,671,680,689,698,707,716,725,734,743,752,761,770,779,788,797,806,815,824,833,842,851,860,869,878,887,896,905,914,923,932,941,950,959,968,977,986,995,1004,1013,1022,1031,1040,1049,1058,1067,1076,1085,1094,1103,1112,1121,1130,1139,1148,1157,1166,1175,1184,1193,1202,1211,1220,1229,1238,1247,1256,1265,1274,1283,1292,1301,1310,1319,1328,1337,1346,1355,1364,1373,1382,1391,1400,1409,1418,1427,1436,1445,1454,1463,1472,1481,1490,1499,1508,1517,1526,1535,1544,1553,1562,1571,1580,1589,1598,1607,1616,1625,1634,1643,1652,1661,1670,1679,1688,1697,1706,1715,1724,1733,1742,1751],{"_40":127,"_128":129,"_130":131,"_132":133,"_134":-5,"_13":-5,"_120":135,"_122":136,"_25":137,"_138":-5,"_139":140,"_141":142},"404 Not Found","slug","404-not-found","url","https://docs.growthloop.com/docs/audience-approval-process","content","[Jump to Content](#content)\n\n[![GrowthLoop](https://files.readme.io/539b4dd-small-GrowthLoop_logo_-_white.png)](https://www.growthloop.com/)\n\n[Guides](https://docs.growthloop.com/docs)[API Reference](https://docs.growthloop.com/reference)\n\n* * *\n\n[![GrowthLoop](https://files.readme.io/539b4dd-small-GrowthLoop_logo_-_white.png)](https://www.growthloop.com/)\n\nPage Not Found\n\nAll\n\nGuides\n\nAPI Reference\n\nPages\n\n###### Start typing to search…\n\n![](https://files.readme.io/3452e08-Group_5.svg)\n\n## Page Not Found","collectionId","2024-03-20T21:02:33.855Z","2025-10-23T18:33:51.377Z","2a97a916-af2c-4765-937a-2dba0e6c96e3","collection","userGroups",[],"channels",[],{"_40":127,"_128":144,"_130":145,"_132":146,"_134":-5,"_13":-5,"_120":147,"_122":136,"_25":148,"_138":-5,"_139":149,"_141":150},"404-not-found-2","https://docs.growthloop.com/destinations","DocumentationAPI Reference\nv\n1.0\nPage Not Found","2024-03-20T21:02:39.411Z","b789cca1-7f99-4dc3-9b1a-dc682897cb3a",[],[],{"_40":127,"_128":152,"_130":153,"_132":146,"_134":-5,"_13":-5,"_120":154,"_122":136,"_25":155,"_138":-5,"_139":156,"_141":157},"404-not-found-3","https://docs.growthloop.com/datasets","2024-03-20T21:02:39.330Z","c7a21454-8b97-429f-91d8-dfd11517b281",[],[],{"_40":159,"_128":160,"_130":161,"_132":162,"_134":-5,"_13":-5,"_120":163,"_122":136,"_25":164,"_138":-5,"_139":165,"_141":166},"Access Audience and Syncs Processing Logs","access-audience-and-syncs-processing-logs","https://docs.growthloop.com/docs/access-logs","Learn how to access logs for your syncs, audiences, and journeys.\n\nThe GrowthLoop platform enables you to automatically export processing logs to your systems by integrating directly with storage buckets in your system of choice. Your team will have full visibility into logs written from Growthloop's system when processing Syncs and Audiences. To get started, simply connect your storage bucket in your GrowthLoop storage settings.\n\nCurrently, we support both:\n\n* Google Cloud Storage (GCS)\n* S3 (AWS)\n\nTo setup S3 as your storage bucket follow these steps:\n\n* Create a new S3 bucket in your AWS account\n * Make sure to block public access\n * Setup a TTL time of your choice to enhance security\n* Create a new access key and secret with access to that bucket.\n\n| Permission | Details |\n| --- | --- |\n| s3:GetObject | Permission to retrieve objects |\n| s3:PutObject | Permission to add object to bucket |\n| s3:ListBucket | Permission to list some or all objects |\n\nTo set GCS as your storage bucket follow these steps:\n\n* Create a new GCS bucket in your account.\n * Make sure to block public access\n * Setup a TTL time of your choice to enhance security\n* Create a service account for a user with the following permissions:\n\n| Permission | Details |\n| --- | --- |\n| storage.objects.list | List objects in a bucket |\n| storage.objects.create | Create objects in a bucket |\n| storage.objects.get | Get objects in a bucket |\n\nOnce you have your bucket ready along with the correct credentials head over to the Organizations tab in the GrowthLoop application.\n\n![](https://files.readme.io/c9d556e-Screenshot_2024-01-23_at_6.16.52_PM.png)\n\nSelect your bucket platform and provide the necessary credentials then hit save. That's it! Our platform will begin syncing processing logs directly to your storage bucket.\n\nNow that your bucket is setup, GrowthLoop will begin writing logs directly to the bucket you provided. Logs will be written to the `batch_errors` directory within your bucket. The most common usage pattern of GrowthLoop's logs are the following:\n\n1. You are in the GrowthLoop interface and looking at audiences with export issues. Or you have received an alert of an audience export issue.\n \n2. Navigate to the specific audience or sync to view `export_id` directly associated with the export that had an issue. Simply navigate to the Exports tab and take a look at the Activity panel.\n \n ![](https://files.readme.io/ea30156-export_logs_batch_id.png)\n3. Click the copy icon to copy the `export_id` to your clipboard.\n \n4. Then navigate to your Storage Bucket and the `batch_errors` directory.\n \n5. Each file will be named with the `export_id` in its title. This is very convenient for looking up particular exports from your audiences.\n \n6. Simply search your storage bucket for the file with `export_id` you copied to clipboard in its title.\n \n7. Open the logs file to view row level processing logs for that particular export and see exactly what happened.\n \n\n* * *\n\nIf you experience any issues or have any questions, please reach out to us at [support@growthloop.com](mailto:support@growthloop.com), and we’ll be in touch shortly!\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:31.801Z","0a67b97f-8acc-417b-9e90-ab92a642e283",[],[],{"_40":168,"_128":169,"_130":170,"_132":171,"_134":-5,"_13":-5,"_120":172,"_122":136,"_25":173,"_138":-5,"_139":174,"_141":175},"Activate data to Adobe Experience Platform | GrowthLoop Docs","activate-data-to-adobe-experience-platform-growthloop-docs","https://docs.growthloop.com/docs/adobe-experience-platform","# Activate data to Adobe Experience Platform\n\nLearn how to connect and send audiences to Adobe Experience Platform (AEP)\n\nIn this article, we'll guide you through connecting Adobe Experience Platform (AEP) to GrowthLoop and exporting your audiences to the destination.\n\nAdobe Experience Platform (AEP) is a centralized data management tool designed to unify customer data across channels. It enables real-time customer profiles and data activation, helping organizations deliver personalized experiences at scale.\n\n* You must have a registered Adobe Experience Platform (AEP) account.\n* You must create a project in the [Adobe Developer Console](https://developer.adobe.com/) and add the **Experience Platform API** to it. This project will provide the required credentials: `Client ID (API Key)` and `Client Secret`. [Click here](https://developer.adobe.com/dep/guides/dev-console/create-project/) to learn how to create one.\n\n> 📘\n> \n> You’ll need `Developer` access to create and/or retrieve your `Client ID (API Key)` and `Client Secret`. If you don’t have the necessary permissions, either ask someone who does to retrieve them for you, or contact your Admin to request access.\n\n1. Log into **GrowthLoop** and click the **Destinations** tab on the left sidebar.\n \n2. Then click **New Destinations** on the upper right side.\n \n3. Next, search for **Adobe Experience Platform** in the destination modal and click **Add Adobe Experience Platform**.\n \n4. Enter the required information in the modal, then click **Create**.\n \n 1. **Destination Name**: This is how the destination will be named and referred to in the app going forward. It’s helpful to make this name marketer-friendly so everyone on your team understands its purpose.\n 2. **Sync Frequency**: The default frequency audiences will be synced to the destination. You can always change the sync frequency during export setup, but this sets the default.\n 3. **Tenant Name** & **Sandbox Name**: They help identify your organization and environment within AEP. The Tenant Name appears in the URL after the “@” symbol, and the Sandbox Name appears after \"sname:\": `https://experience.adobe.com/#/@TENANT_NAME/sname:SANDBOX_NAME/`.\n 4. **Organization ID**: This is the unique identifier for your organization within AEP. To find yours, go to the [Adobe Admin Console](https://adminconsole.adobe.com/) and look at the URL in your browser - the Organization ID appears at the end of the URL and ends with `@AdobeOrg`. Be sure to copy the entire string, including `@AdobeOrg`: `https://adminconsole.adobe.com/123456789@AdobeOrg/overview`\n 5. **Client ID (API Key)** & **Client Secret**: These credentials are required to authenticate your application and securely connect to Adobe’s APIs. To access them, go to [Adobe Developer Console](https://developer.adobe.com/), click on `Console`, then `Projects`, and select the appropriate one. Inside the project, scroll to the `Credentials` section. There, you can copy the Client ID and click `Generate access token` to create a Client Secret.\n 6. **Namespace**: A namespace defines the ID type used to match profiles - like `\"Email\"`, `\"Phone\"`, `\"IDFA\"`, `\"GAID\"`, `\"ECID\"`, `\"Adobe Analytics\"`, `\"FCM\"`, `\"AdCloud\"`, `\"TNTID\"`, `\"Windows AID\"`, and `\"APNS\"`. If you select `\"Custom Namespace\"`, you’ll need to enter a valid namespace ID below that already exists in your AEP account.\n 7. **Custom Namespace ID (Optional)**: A Custom Namespace ID is a unique identifier you've registered in AEP to represent your own identity type (e.g., a loyalty ID). If you select `\"Custom Namespace\"` in the dropdown above, you must enter the corresponding `Identity Symbol` exactly as it appears in AEP. You can find your list of custom namespace IDs under `Adobe Experience Platform > Identities`.\n\n5. Navigate to your list of audiences by clicking the **Audiences** tab on the left sidebar.\n6. Choose an existing audience or create a new one.\n\n> 📘\n> \n> Need help creating an audience? Click [here](https://docs.growthloop.com/docs/create-an-audience) to learn how!\n\n7. Once created, click the **Export** button on the upper right side.\n8. Search for **Adobe Experience Platform** in the export modal and then click **Select**.\n9. Under **Configure Match Field Settings**, select the appropriate fields from your primary dataset to match customer identities.\n\n> 📘\n> \n> The available match fields in the export setup are automatically set based on the identity namespace selected in the destination configuration. For example, if `\"Email\"` is selected as the namespace, only the **Email** field will be available as the match field during export. However, if you select `\"Custom Namespace\"`, the **Unique ID** field will be available instead, allowing you to map your own customer identifier.\n\n10. Now, set up your export settings:\n 1. **Export Name**: Automatically populated with your audience name for easy identification in the destination.\n 2. **Campaign Type**: Choose between `One Time` to export the audience once or `Ongoing` to continuously export new audience members as they qualify.\n 3. **Export Inclusion Criteria**: Choose between `All audience members` to export the full audience or `Newly added audience members` to export only those who have been added since the last export.\n 4. **Namespace**: Displays the `Identity Symbol` entered during the destination setup. This field is disabled because the namespace was predefined when the destination was configured and must remain fixed to ensure consistency in the schema that will be created during your first export. To use a different identity type, you must create a new destination configuration with the desired namespace.\n 5. **Export Schedule**: Configure the `Frequency`, `Start Date`, `End Date`, and specific `Days of the Week` (only for `Ongoing` exports).\n 6. **Additional Fields**: Add extra fields to your export for personalization, with the option to alias the output for further customization.\n11. Finally, click **Export** to send your audience to the destination!\n\n> 📘\n> \n> * A new schema will be created in AEP the first time you export to a specific destination and namespace combination. The schema name will begin with the prefix `gl_audience` and can be found under **Schemas** in the **Data Management** section of AEP.\n> * The namespace specified will be used as the **primary identity** for the schema. For example, if you selected `Email` as the namespace, the schema will use `Email` as the primary identity field.\n> * Future exports using the same destination and namespace will reuse this schema but generate a new dataset. The identity namespace and primary identifier cannot be changed once the schema is created - if you need to use a different one, you must create a new destination configuration.\n\nTo view your audience, log in to Adobe Experience Platform and navigate to the **Audiences** page under the **Customers** section in the left-hand navigation. There, you’ll find your audience listed with the prefix `gl_`.\"\n\n> 📘\n> \n> Adobe typically processes batch exports within minutes to a few hours. While the data becomes available in Profile relatively quickly, it won’t appear in the audience until Adobe runs the batch audience evaluation, which occurs daily on a predefined schedule.\n\n![](https://files.readme.io/3005878ba587f76d1404723d5eccc0c49bb3eda6be23a8833a14226e7b873211-image.png)\n\n> 👍\n> \n> You've successfully created an export to AEP!\n\n> 📘\n> \n> Experiencing any issues when connecting to Adobe Experience Platform (AEP)? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and we’ll be in-touch shortly to help resolve the matter!\n\nUpdated 4 months ago\n\n* * *","2024-03-20T21:02:36.348Z","a0cad7b8-80c0-46c5-8180-bc325686fa15",[],[],{"_40":177,"_128":178,"_130":179,"_132":180,"_134":-5,"_13":-5,"_120":181,"_122":136,"_25":182,"_138":-5,"_139":183,"_141":184},"Activate data to Salesforce Marketing Cloud | GrowthLoop Docs","activate-data-to-salesforce-marketing-cloud-growthloop-docs","https://docs.growthloop.com/docs/salesforce-marketing-cloud","# Activate data to Salesforce Marketing Cloud\n\nLearn how to set up Salesforce Marketing Cloud as a destination so you can start exporting audiences to it.\n\nThis article outlines the steps necessary to set up Salesforce as a GrowthLoop destination and begin exporting audiences for activation.\n\nIn this Help Center article, we will walk you through the steps to get Salesforce Marketing Cloud connected as a destination in the GrowthLoop web application. Once connected, you will be able to send your audience segments to SFMC for marketing activation!\n\nTo connect the GrowthLoop application to the Salesforce Marketing Cloud destination, there are a few items required for setup within SFMC. We will walk through the steps below:\n\n* Configure SFMC user permissions\n* Create API integration\n* Configure Data Extensions Permissions\n\nAfter creating a new user in Salesforce Marketing Cloud, make sure the user is an administrator in the SFMC environment. The permission required is called _**Installed Package | Administer**_ in the SFMC permissions UI. If the user has the correct permissions, we would be able to see a **Setup** dropdown when you click on the user profile in the top right corner of the UI. Click on name in profile and click **Setup**.\n\n![](https://files.readme.io/774100b-sfmc_settings.png)\n\nNavigate to **Platform tools** and then **Installed Packages.** If you cannot see “Installed Packages” in the dropdown, you must install that App.\n\n![](https://files.readme.io/d3cc847-sfmc_installed_packages.png)\n\nUnder settings, click **Setup**. In the menu on the left, click on **Apps** and then click **Installed Packages**.\n\nChoose **New**, and enter a name, for example, **GrowthLoop API**. Add an optional description of the API integration if you’d like.\n\n![](https://files.readme.io/2539640-sfmc_package_details.png)\n\nConfigure these fields:\n\n* Component: API\n* Integration: server-to-server\n\n![](https://files.readme.io/95020c1-smfc_component_api.png)\n\nNext, click **Edit** to edit the API integration permissions. A popup will appear with Channels and Assets permissions. Ensure that _**all**_ of the boxes are checked to provide the necessary API permissions.\n\n![](https://files.readme.io/a08be74-sfmc_permissions.png)\n\nAdd read and write permissions for data extensions in the Salesforce application.\n\nReturn to the GrowthLoop application at [https://app.flywheelsoftware.com](https://app.flywheelsoftware.com/). Log in using your company email, and you will be brought to the audiences page. On the left, click on the **Destinations** tab. Click **Connect Destination** and scroll down to select **Marketing Cloud**.\n\nEnter the destination name and select a sync frequency. These configurations can be changed at a later time if need be.\n\n![](https://files.readme.io/4a537c9-sfmc_configuration.png)\n\nNext, you will be asked to enter API configuration information. You can find the required information in SFMC where you configured the API integration.\n\n![](https://files.readme.io/9f8357a-sfmc_required_credentials.png)\n\n1. Subdomain: This is a subset of the **authentication base URI** \\*before **\\***.auth and _after_ https://\n2. Client ID\n3. Client Secret\n\n![](https://files.readme.io/6ffba6d-sfmc_config_zoom.png) ![](https://files.readme.io/9038f12-sfmc_config_zoom.png)\n\nClick **Create**. You now have your SFMC destination connected to the GrowthLoop application. You are ready to export audiences to Salesforce Marketing Cloud in one click!\n\nWhen exporting an audience to SFMC, you have the option to export zero or more personalization fields.\n\n![](https://files.readme.io/696749e-image.png)\n\nThese fields are exported as **String** type onto SFMC. However, if you'd like to preserve your data types when exporting to SFMC, you can contact your GrowthLoop rep to have this enabled for your account.\n\nGrowthLoop currently allows you to preserve the following data types when passing them to SFMC, and we'll be adding more to the mix.\n\n1. **Email** -- Your data column name should be set as **Email** (case insensitive). If you don't have that in our current data configuration, your GrowthLoop rep can help you with that using GrowthLoop's Models.\n2. **Date** -- The type of this field in your warehouse must be **Date type** and other types such as **datetime** will not be preserved\n3. **Text** -- There are not caveats for this data type.\n\nNavigate to your SFMC instance and under the **Subscribers** tab, click into Data Extensions and find the audience in the **GrowthLoop Syncs** folder.\n\n![](https://files.readme.io/d26e79d-image.png)\n\nIf you have any questions or are experiencing any issues connecting to Salesforce Marketing Cloud as a destination, please reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and we’ll be in touch shortly!\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:29.651Z","3c8d80b5-af84-4713-8275-ee7d834c9e83",[],[],{"_40":186,"_128":187,"_130":188,"_132":189,"_134":-5,"_13":-5,"_120":190,"_122":136,"_25":191,"_138":-5,"_139":192,"_141":193},"Add SFTP as a destination | GrowthLoop Docs","add-sftp-as-a-destination-growthloop-docs","https://docs.growthloop.com/docs/sftp","# Add SFTP as a destination\n\nSend your GrowthLoop audience segments via SFTP\n\nIn this article, we will walk you through the steps to get SFTP connected as a destination in the GrowthLoop web application. Once connected, you will be able to send your audience segments via SFTP for marketing activation!\n\n* **Obtain the FTP server credentials** from the administrator, including the username and password. For anonymous FTP, this usually means using \"anonymous\" as the username and your email address as the password.\n* **Know the hostname or IP address** of the FTP server you need to connect to.\n* **Verify the port number** used by the FTP server (default is 21 for FTP and 22 for SFTP).\n* **Have the folder path ready** if the FTP server requires uploading files to a specific folder.\n\n> 📘\n> \n> **Note**: You can choose to authenticate using either Username & Password or an SSH Key\n\n1. When you sign into the GrowthLoop platform, navigate to the **Destinations** tab on the left sidebar and click **New Destination** in the top right corner.\n2. When the **Select Destination** window pops up, type **SFTP** into the search bar and click **Add SFTP**.\n3. Clicking **Add SFTP** will require you to select/insert the following information:\n 1. `Destination details`\n 1. **Destination Name**: This is how the destination will be named and referred to in the app going forward.\n 2. **Sync Frequency**: This indicates how frequently audiences will be synced to the destination.\n 2. `Credentials`\n 1. **Username:** Enter the username provided by your FTP server administrator. If the server uses anonymous access, you may enter \"anonymous.\"\n 2. **Password:** Enter the password associated with the username. For anonymous access, this is often your email address.\n 3. **SSH Key:** Enter the private SSH key provided by your administrator if key-based authentication is required.\n 4. **SSH Key Password:** If your SSH key is password-protected, enter the password here. Leave blank if your key does not require one.\n 5. **SSH Key Algorithm:** Select the algorithm used to generate your SSH key (e.g., RSA/GPG or ED25519).\n 3. `Upload Settings`\n 1. **Host:** Input the FTP server's hostname or IP address. Ensure this is correct to avoid connection issues.\n 2. **Port:** Specify the port number. The default for FTP is 21. If you are using SFTP (secure FTP), the port is typically 22.\n 3. **Upload Folder:** If required, enter the path to the specific folder on the server where files should be uploaded. This is optional and depends on the server’s configuration.\n 4. `File Format`\n 1. **Format:** Select the file format for export. Currently supported: _Delimited_.\n 2. **Delimiter:** Specify the character that separates values in the file (e.g., , for CSV, \\\\t for TSV).\n 3. **File Extension:** Enter the file extension to be used for the exported file (e.g., csv, tsv).\n 4. **Encryption Algorithm:** Choose the encryption method for securing exported files (e.g., PGP). Leave blank if no encryption is required.\n 5. **Encryption Key:** Enter the encryption key corresponding to the selected algorithm.\n 6. **Prefix for Personalization Fields:** Define a prefix (e.g., fw) that will be added to personalization fields in the exported file.\n 7. **Columns to Export (Comma-separated list):** Specify which columns to include by entering names separated by commas. Leave blank to export all columns.\n 8. **Exclude Internal Fields:** Select this option to omit system-generated internal fields from the export.\n 9. **Exclude Headers:** Select this option to export data without including header rows.\n4. Go ahead and select **Create**, and we’ll validate we have all the proper permissions to load audience data to **SFTP**. You should now see **SFTP** in your list of connected destinations!\n\n5. Navigate to your list of audiences by clicking the **Audiences** tab on the left sidebar.\n6. Choose an existing audience or create a new one. Need help creating? Click [here](https://docs.growthloop.com/docs/create-an-audience) to learn how!\n7. Once created, click the **Export** button on the upper right side.\n8. Search for **SFTP** in the export modal and **Select** it.\n9. Map **Email** under Configure Match Field Settings if it's not already. Then Click **Next**.\n10. Configure your export settings:\n * **Export Name**: Automatically populated with your audience name for easy identification in the destination.\n * **Campaign Type**: Choose between a one-time export or ongoing basis.\n * **Export Schedule**: Set the frequency, start date, end date, and specific days of the week.\n11. Lastly, click **Export**. Congrats on successfully exporting an audience via SFTP!\n\n> 📘\n> \n> Experiencing any issues when connecting to **SFTP**? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and we’ll be in-touch shortly to help resolve the matter!\n\nUpdated about 2 months ago\n\n* * *","2025-06-20T22:59:02.206Z","c18d4cc7-3bd5-47e4-93db-86d84e073694",[],[],{"_40":195,"_128":196,"_130":197,"_132":198,"_134":-5,"_13":-5,"_120":199,"_122":136,"_25":200,"_138":-5,"_139":201,"_141":202},"AI-empowered generative marketing | GrowthLoop Docs","ai-empowered-generative-marketing-growthloop-docs","https://docs.growthloop.com/docs/overview-2","## Overview\n\nAn introduction to Generative Marketing\n\nThe core idea of Generative Marketing is simple. Empower your marketing teams to harness the power of Generative AI to increase their ability to run a full campaign experiment cycle: Targeting, Journey Orchestration, Creative, and Insights gathering.\n\nThe central tenet of Generative Marketing is that a **marketer is always in the Loop**. Generative AI is not here to replace what marketing teams do. Generative AI is meant to assist, empower, and amplify what a team of marketers can do for their customers. Instead of 95% of marketing concepts gathering dust on a shelf and taking 6 months to launch a single journey campaign, generative marketing has the potential to reduce technical barriers so small marketing teams can launch and test all of their messaging concepts.\n\n**Marve Studio Generative Targeting**\n\nIt all starts with Generative Targeting. Imagine your teams being able to harness the power of AI to brainstorm which audiences they should target to achieve their goals? This is now possible with Marve Studio.\n\n**Generative Journeys & Creative**\n\nWe are holding a private preview in partnership with Google on the next phase of Generative Marketing including generating creative for marketing campaigns and full journey sequence drafts for your marketing team. You can see an early preview here.\n\nThis is just the beginning. Generative Marketing will become your team's marketing assistant to enable them 10x the number of campaign experiments they run each year.\n\nIf you want to learn more please contact [support@growthloop.com](mailto:support@growthloop.com).\n\nUpdated 5 months ago\n\n* * *\n\nLearn how to use Marve Studio Generative Targeting\n\n* [Marve](https://docs.growthloop.com/docs/marve)","2024-03-20T21:02:31.112Z","16604fad-4c6f-44b7-92fd-33ceb0e12052",[],[],{"_40":204,"_128":205,"_130":206,"_132":207,"_134":-5,"_13":-5,"_120":208,"_122":136,"_25":209,"_138":-5,"_139":210,"_141":211},"Attentive","attentive-2","https://docs.growthloop.com/docs/attentive-destination","In this Help Center article, we will walk you through the steps to get **Attentive** connected as a destination in the GrowthLoop web application. Once connected, you will be able to send your audience segments to Attentive for marketing activation!\n\nBefore you begin this process, you must have an [Attentive SFTP account](https://docs.attentive.com/pages/developer-guides/sftp-solution/connect-to-attentive-sftp/) set up for you. If you haven’t yet requested an SFTP account, please contact your designated Client Strategy team member or our White Glove team [whiteglove@attentivemobile.com](mailto:whiteglove@attentivemobile.com)\n\nYou will be required to provide an email address that will be used to manage the SFTP account and reset the password.\n\nWhen you sign into the GrowthLoop, navigate to the **Destinations** tab on the left sidebar and click **New Destination** in the top right corner\n\n![](https://files.readme.io/6685e4e-Screenshot_2024-01-25_at_11.24.20_AM.png)\n\nWhen the **Select Destination** window pops up, scroll to find Attentive or Type in the search box and click **Add**.\n\n![](https://files.readme.io/beaa8f1-Screenshot_2024-02-06_at_9.30.04_AM.png)\n\nClicking “Add Attentive Mobile” will pop up a window with **configuration settings**. You’ll need to select/insert the following information:\n\n![](https://files.readme.io/1221e69-Screenshot_2024-02-06_at_10.11.02_AM.png)\n\n* **Destination Name:**This is how the destination will be named and referred to in to the app going forward\n* **Sync frequency**: how frequently audiences will be synced to the destination\n* **Client Domain:** URL used to access your Attentive application.\n* **FTP Username:** this is your Attentive Username when setting up your SFTP account. You’ll need to contact your Account Manager for this if you already haven’t done so.\n* **FTP Password:** this is your Attentive FTP Password when setting up your SFTP account. You’ll need to contact your Account Manager for this if you already haven’t done so.\n\nGo ahead and select **Create**, and we’ll validate we have all the proper permissions to load audience data to Attentive.\n\nYou should now see Attentive in your list of connected destinations! To view this in the GrwothLoop App, navigate to the **Destinations** Tab in the **left sidebar**. You’ll see a list of all your destinations.\n\n![](https://files.readme.io/122a3a8-Screenshot_2024-02-06_at_10.00.58_AM.png)\n\nNow let’s **export an audience** to Attentive. Click on Audiences in the left side bar, and choose the audience you’d like to export.\n\n![](https://files.readme.io/cc42d42-Screenshot_2024-02-06_at_10.18.46_AM.png)\n\nClick the **Export Audience** button in the top right, and select **Attentive**. You’ll be prompted next to configure **match field settings.**\n\n![](https://files.readme.io/9dba471-Screenshot_2024-02-06_at_10.24.14_AM.png)\n\nNow let’s configure the **Match Field(s) and Export Settings**.\n\nLet’s start with **Export Settings.**\n\n* **Export Name:** Give a name to your export for easy reference.\n* **Campaign Type:** Choose between Ongoing (continuous campaign with no end date) and One Time (for a single export).\n* **Frequency:** Decide how often you want to update audience membership and send it to Attentive. Options include Every Fifteen Minutes, Thirty Minutes, Hourly, Daily, Weekly, and Monthly.\n* **Start:** The default is to start Now, but you can choose a specific time from the dropdown.\n* **End:** The default is to end Never, but you can choose a specific time from the dropdown if needed. \n ![Screenshot 2024-02-06 at 10.40.37 AM.png](https://files.readme.io/6e52075-Screenshot_2024-02-06_at_10.11.02_AM.png)\n\nWith **Attentive Mobile** the only available **Match** **Field** is **Phone Number**, these will need to be 1:1 so from the drop down you’ll want to select the field on your customer table that represents the customer’s “Phone number”.\n\n![](https://files.readme.io/a173e3d-Screenshot_2024-02-06_at_10.28.55_AM.png)\n\nClick **Export** and you’ll see Active Export in Green to verify export is live.\n\n![](https://files.readme.io/6368fea-Screenshot_2024-02-01_at_5.22.20_PM.png)\n\nWhen you export an audience to Attentive, you can log in to your Attentive account and navigate to the **Audience > Segments** tab in the left sidebar. Here, you will find your newly exported audience in the list. _Depending on the size of the audience, exports can take up to 30 minutes to populate._\n\n![](https://files.readme.io/b255878-Screenshot_2024-02-06_at_10.00.58_AM.png)\n\n**Checking export activity** on your previously exported audiences is easy. Navigate to any previous exported audiences and click the Exports tab to check the progress of all your export activity.\n\n![](https://files.readme.io/5e85d56-Screenshot_2024-02-06_at_10.57.08_AM.png)\n\n**Congratulations! You’ve now successfully connected Attentive as a destination, and set up an active audience export within GrowthLoop!**\n\nExperiencing any issues when connecting to Attentive? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and we’ll be in-touch shortly to help resolve the matter!\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:36.847Z","840c48a9-a7a3-404d-920f-34df3b900c33",[],[],{"_40":213,"_128":214,"_130":215,"_132":216,"_134":-5,"_13":-5,"_120":217,"_122":136,"_25":218,"_138":-5,"_139":219,"_141":220},"Audience Comparisons: Identify overlap | GrowthLoop Docs","audience-comparisons-identify-overlap-growthloop-docs","https://docs.growthloop.com/docs/audience-comparison","## Audience Comparison\n\nLearn how to identify pre-existing Audiences that overlap with your current audience criteria!\n\nWhen creating a new audience, it’s helpful to know if similar audiences already exist. Overlapping audiences can impact targeting efficiency and campaign performance. In this article, you’ll learn how to identify pre-existing audiences that share criteria with your current selection, helping you make more informed decisions. This will also cover selecting an audience to be excluded from your criteria.\n\n1. Select **Audiences** from the left sidebar and click **New Audience** in the top-right corner.\n2. Select a **Dataset Group** to create the audience from, then choose a **Build** option. We recommend **Start with the basics**.\n3. In the right-hand frame, go to the **Comparisons** tab. The **Top Overlap Audiences** section will load automatically, ranking audiences from the highest to lowest overlap.\n\n> 📘\n> \n> The color-coded overlap percentages help you identify similar pre-existing audiences, allowing for more efficient targeting and budget use:\n> \n> 1. Red (High Overlap): More than 66% overlap\n> 2. Yellow (Medium Overlap): 33% - 66% overlap\n> 3. Green (Low Overlap): Less than 33% overlap\n\n4. Click on an audience name and select **Exclude** to remove it from your current audience.\n5. The excluded audience will appear in the criteria list at the top, with **where not** automatically applied.\n\nIn addition to excluding audiences, you can also pin selected audiences for ongoing evaluation. Here's how:\n\n1. In the **Comparisons** tab, click on an audience name from the **Top Overlap Audiences** list.\n2. In the modal, select **Add as Target Audience** - it will then appear as a tile above **Top Overlap Audiences**, displaying both overlap percentage and count.\n\n> 📘\n> \n> You can pin up to **3 audiences** for overlap measurement.\n\n3. As you modify audience criteria, the overlap percentages and counts will update in real time\n4. Once satisfied with your audience, click the Ellipsis (⋮) on a pinned audience tile to either:\n 1. **Exclude** the audience from your current build.\n 2. **Remove** it from the pinned audience section.\n\nNow you have the tools to identify, exclude, and track overlapping audiences for more efficient targeting and better campaign performance. Try it out and optimize your audience strategy today!\n\n> 📘\n> \n> If you experience any issues, please reach out to us at [support@growthloop.com](mailto:support@growthloop.com), and we’ll be in touch shortly to help resolve the matter!\n\nUpdated 5 months ago\n\n* * *","2025-06-20T22:58:32.384Z","5517ad2e-35a4-45d5-b8b5-85e01ee79eac",[],[],{"_40":222,"_128":223,"_130":224,"_132":225,"_134":-5,"_13":-5,"_120":226,"_122":136,"_25":227,"_138":-5,"_139":228,"_141":229},"Audience insights | GrowthLoop Docs","audience-insights-growthloop-docs","https://docs.growthloop.com/docs/audience-insights","In this help doc, we'll show you how you can easily bring all your marketing campaign data (paid media and emails) into GrowthLoop and see your audience performance data in one place.\n\nGrowthLoop makes it easy to track the performance of your marketing campaigns from start to finish. Whether you're running campaigns on platforms such as Google Ads, Facebook Ads, TikTok or other paid media channels, or email platforms like Sailthru and Iterable and others, GrowthLoop gives you actionable insights—all in one place.\n\nFurthermore, your campaign data will automatically be tied back to their respective audiences in GrowthLoop.\n\n \n\n1. For every platform you'd like to ingest your campaign data, click **Ingest** on the left hand menu, and add that source as a new ingest source.\n\n![](https://files.readme.io/e106c7ddf12b43f1c5eb56b221dfcaa6fb762643128eb91e567d46b8a70723fa-image.png) \n![](https://files.readme.io/d1566c90e04a1054a352eedea61cf9470999b96c14654bd7ba2e55ff566d9e93-image.png)\n\n2. For each selected source, you'll be guided on authenticating into the platform and how you'd like to configure your specific source ingestion. For example you can choose to only bring the last 90 days of your campaign data or the last full year. \n Once you've setup your ingestion you can see them in your list of ingests with the appropriate status. At first you'll see it as **Processing** before it becomes **Active**\n\n![](https://files.readme.io/29745724fb5d50bf53cba1a859cf8f562e70f4cd9c4f9e1a513f9d41d8a75966-image.png)\n\nYour ingested campaigns are automatically tied to their corresponding audiences in GrowthLoop.\n\nAfter your ingested source turns **Active**, give GrowthLoop up to 30 minutes to properly connect all the ingested data to their corresponding audiences.\n\nNow, if an audience is exported to the ingested source and you have ran campaigns against that audience, you can see those results under the **Insights** tab under the audience\n\nFor example the audience below was exported to both Sailthru and Iterable with a small campaign ran against it.\n\n![](https://files.readme.io/cce7d43756c1a0fe0816f137ab4be71240ad40c4e02a1a64011faa0f8d5d37f6-image.png)\n\nFollowed by this audience which was exported to Google ads and Facebook\n\n![](https://files.readme.io/a35c566785795de5b15c25fee3c02e07eb8cb7689ed47cbee86ab6aed416c72d-image.png)\n\nYou will notice that Email and Paid media channels report on metrics that are relevant to those platforms.\n\nFor Email channels you get metrics such as:\n\n* Sends\n* Opens\n* Clicks\n* Unsubscribe\n* Bounce\n* And their responsive **rates** to sends\n\nFor paid performance channels you get metrics such as:\n\n* Spend\n* Impression\n* Clicks\n* Conversion\n* And their respective **rates** to all views\n\nYour ingestions will continue to run moving forward.\n\nUpdated 9 days ago\n\n* * *","2025-06-20T22:58:31.510Z","6455d2f3-f48d-4a24-8a69-f255f156c666",[],[],{"_40":231,"_128":232,"_130":233,"_132":234,"_134":-5,"_13":-5,"_120":235,"_122":136,"_25":236,"_138":-5,"_139":237,"_141":238},"Audiences","audiences-2","https://docs.growthloop.com/reference/audiences","The Audiences API allows you to fetch and interact with audiences in the GrowthLoop Platform.\n\nHead over to the GrowthLoop app in the organization section and generate a new API key.\n\n![](https://files.readme.io/c01de0e-Screenshot_2024-01-25_at_9.49.41_AM.png)\n\nThe API key is then provided to the API in the following format: `'Bearer token=your_secret, access_key=your_key'`","2024-03-20T21:02:21.190Z","edf54980-25c6-48b5-9dd3-17af00635aee",[],[],{"_40":240,"_128":241,"_130":242,"_132":243,"_134":-5,"_13":-5,"_120":244,"_122":136,"_25":245,"_138":-5,"_139":246,"_141":247},"Audiences: 3 types and ways to build them | GrowthLoop Docs","audiences-3-types-and-ways-to-build-them-growthloop-docs","https://docs.growthloop.com/docs/intro-to-audiences","# Audiences: 3 types and ways to build them\n\nYou've seen them, you've heard about them, or maybe you've used them but still have questions? No worries! In this tutorial, you'll learn the main differences between between starting with the basics, building with a recipe, and building from scratch.\n\nFirst off, what's an audience? An audience in the GrowthLoop Audience Platform is a group of customers whose actions, inactions or attributes match a set of criteria you've defined, sometimes known as segments or lists. Here's a few examples of audiences you could create:\n\n* **New customers** exhibiting behaviors that indicate high potential value.\n* **Existing customers** that are at risk of churning.\n* **Previous customers** that stopped buying 90 days ago.\n\nOnce you've created your desired audiences, you can target them across different marketing channels such as Email, Facebook, Google Adwords, and more with a couple clicks. In addition, you can track [revenue uplift](https://docs.growthloop.com/docs/experiments) for each audience you target and measure true ROI.\n\nThere are three types of audiences in the GrowthLoop Audience Platform: Start with the **basics**, build with a **recipe**, and build from **scratch**.\n\n‍\n\nStart with the **basics** allows you to begin building your audience with pre-populated default filters and other customizations which can be edited to suit your needs by your GrowthLoop administrator.\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd843db581cb37_H5KZWdlsvh06khhB536QYZDN9WKrO1yJ1FR88xHB8RUPjsLkUZavHmRzcxSwaglCAJ0EfKvNpnx1WkrDz6XhIGCMkPofbeFJVQ07Nwunjex4cL5BUToLD7us2dpK9UJ8ORfVuhnyYi57UUXPqqt80Qg.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd843db581cb37_H5KZWdlsvh06khhB536QYZDN9WKrO1yJ1FR88xHB8RUPjsLkUZavHmRzcxSwaglCAJ0EfKvNpnx1WkrDz6XhIGCMkPofbeFJVQ07Nwunjex4cL5BUToLD7us2dpK9UJ8ORfVuhnyYi57UUXPqqt80Qg.png)\n\n‍\n\n‍\n\nRecipes are suggestions that take into account your industry, goals, and prior success as well as data points available in your data cloud. Select the recipe that works for your use case and goals. [GrowthLoop Recipes](https://www.growthloop.com/recipes) empowers your business teams to unlock proven customer segments improving performance and decreasing time to market.\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd847e8881cb38_nGwmzqyia_ZVlxa2P8jFPFwFtwJv910eD3ZwgzIdVINmlNwwIzkIhyvzGjSHBXJ3CmVWzCh6M8gk04e_TYO2p__bbjGM6s1nR79PwCXgV8jOtjsFPfl0SsmPMaqlt1hH7641X6Jmz5spUa6V2NOl8nY.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd847e8881cb38_nGwmzqyia_ZVlxa2P8jFPFwFtwJv910eD3ZwgzIdVINmlNwwIzkIhyvzGjSHBXJ3CmVWzCh6M8gk04e_TYO2p__bbjGM6s1nR79PwCXgV8jOtjsFPfl0SsmPMaqlt1hH7641X6Jmz5spUa6V2NOl8nY.png)\n\n‍\n\nBuilding from scratch gives you a blank canvas for starting your new audience.\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd842c0681cb3a_6Ghf9kfgy42LP5778i-otfPE47aT6KuAVte2d4Oyv_iyMvM8cZ63NarQKiikzOC49fJf2QatUbByw4IdG79L_HIJVjsDLh-WO1NqYqcSy4gohiaurfcdMty4yWpbIVZ-7MQGZhXb-m0IeA47SBIGq2k.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd842c0681cb3a_6Ghf9kfgy42LP5778i-otfPE47aT6KuAVte2d4Oyv_iyMvM8cZ63NarQKiikzOC49fJf2QatUbByw4IdG79L_HIJVjsDLh-WO1NqYqcSy4gohiaurfcdMty4yWpbIVZ-7MQGZhXb-m0IeA47SBIGq2k.png)\n\n‍\n\nNow that you know the difference between starting with the **basics**, building with a **recipe**, and building from **scratch**, how do you access, create, or modify them? Check out the [Create an Audience](https://docs.growthloop.com/docs/create-an-audience) tutorial for step-by-step instructions!\n\nUpdated 5 months ago\n\n* * *\n\n* [Create an Audience](https://docs.growthloop.com/docs/create-an-audience)","2024-03-20T21:02:24.239Z","1c7822db-f13c-4886-8c42-d8d8c02f6605",[],[],{"_40":249,"_128":250,"_130":251,"_132":252,"_134":-5,"_13":-5,"_120":253,"_122":136,"_25":254,"_138":-5,"_139":255,"_141":256},"Audiences: Best practices to stay organized | GrowthLoop Docs","audiences-best-practices-to-stay-organized-growthloop-docs","https://docs.growthloop.com/docs/organize-audiences","# Audiences: Best practices to stay organized\n\n## Organizing your audiences\n\nAs you start to use GrowthLoop more and more within your organization, your list of audiences can start to get unruly. Learn how to best organize your audiences, search for active audiences and some time-saving tips to quickly get back to the information you need when you need it.\n\nWhen you first create your audience, you will want to use a name that is descriptive enough for you, or others, to recognize it. Including some indication of the filter criteria, key campaigns, or audience identifiers will help you. There is no need to use your initials, the destination, or the dataset group in the name as those all can be applied as filters on the audiences page.\n\n![](https://files.readme.io/25ec6dc-Untitled.png)\n\nTagging can help you better organize your audiences and group audiences together that fall under a specific category. Tagging audiences also offers the ability to quickly find all audiences with that tag under the left navigation.\n\nWhen you first build an audience, or you return to an already built audience, you will see the ability to tag that audience directly under the audience name. After you have entered your intuitive audience name, you can apply the tag.\n\n![](https://files.readme.io/8802d9d-Untitled_1.png)\n\nWhen you first click on the “Add tags” button you will get a list of all available tags. From here you can select one or many of the available tags or you can type directly into the “Search or add a value” text box to find your tag or create a tag on the fly.\n\n![](https://files.readme.io/c26c1d5-Untitled_2.png)\n\nAfter you have created all your tags, or selected from the available tags, you will notice that they appear on the audience view. These tags have now been applied to your audience and are grouped with other audiences having the same tag.\n\n![](https://files.readme.io/8bdfb14-Untitled_3.png)\n\nNow that you have intuitive audience names and you have applied your tags it becomes very simple to find your audiences.\n\nFrom the audiences page simply search for the name or apply any of the available filters to narrow the list of audiences down to the ones you are specifically looking for. Your available filters are Name, Audience type (Template or Audience), Status, Tags, Dataset Group, Destination, and Creator.\n\n![](https://files.readme.io/e64ef89-Untitled_4.png)\n\nYou can also use our express tag search to quickly get to your tagged audiences. On the left hand navigation panel, click the “>” icon next to the “Audiences” navigation item.\n\n![](https://files.readme.io/f127abe-Untitled_5.png)\n\nFrom there, you will see all your available tags. Clicking on one of the tags will bring you to the audiences page with all the audiences having that tag applied.\n\n![](https://files.readme.io/c4634d0-Untitled_6.png) ![](https://files.readme.io/b9e69c3-Untitled_7.png)\n\nCongrats! You have successfully organized all your audiences and now have an easy and intuitive way of finding them when needed.\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:26.236Z","5ca4c573-102d-4636-b55f-71b2d170e4ca",[],[],{"_40":258,"_128":259,"_130":260,"_132":261,"_134":-5,"_13":-5,"_120":262,"_122":136,"_25":263,"_138":-5,"_139":264,"_141":265},"Audiences: Centralize, segment, and activate | GrowthLoop Docs","audiences-centralize-segment-and-activate-growthloop-docs","https://docs.growthloop.com/docs/audiences-overview","# Audiences: Centralize, segment, and activate\n\n## Overview\n\nLearn how to build audiences\n\nGrowthLoop audiences serves as your composable audience management system. You can build audiences directly on your data cloud, and use them anywhere in your business.\n\n![](https://files.readme.io/8537fbd-Screenshot_2024-01-25_at_9.28.30_AM.png)\n\nToday, many organizations are building audiences in 10+ systems. This creates inefficiencies in targeting, confusing user experiences, and disjointed measurement. GrowthLoop audiences was designed to consolidate these silos.\n\nGrowthLoop audiences is a centralized audience management layer that any team member can use to segment customers, share their audiences with each other, and then activate in their platform of choice.\n\n![](https://files.readme.io/be45034-2024-01-25_09.31.47.gif)\n\nUpdated 5 months ago\n\n* * *\n\n* [Intro to Audiences](https://docs.growthloop.com/docs/intro-to-audiences)\n* [Create an Audience](https://docs.growthloop.com/docs/create-an-audience)","2024-03-20T21:02:24.143Z","119795c9-d920-4e7e-8b5d-c28cb9ee7cc9",[],[],{"_40":267,"_128":268,"_130":269,"_132":270,"_134":-5,"_13":-5,"_120":271,"_122":136,"_25":272,"_138":-5,"_139":273,"_141":274},"Audience Sharing: Set up your notifications | GrowthLoop Docs","audience-sharing-set-up-your-notifications-growthloop-docs","https://docs.growthloop.com/docs/audience-sharing","# Audience Sharing: Set up your notifications\n\nWe understand that building new audiences can be an exciting and collaborative process, but it shouldn't come at the cost of constant notification overload. Our Audience Sharing Feature promises better default behaviors and gives you granular control over how notifications are disseminated. You can now share your Audiences with selected teams or individual team members. Not only that, you can also provide view-only or edit access as you share your audiences.\n\nGetting started with Audience Sharing Feature is simple:\n\n1. **Audience Sharing Settings**\n\nThe settings for Audience Sharing are in the organization panel. This is where you determine whether you want to automatically or manually share audiences.\n\n![](https://files.readme.io/6d55500-Untitled.png)\n\nUnder **Default Audience Sharing:**\n\n* If **automatically share new audiences with team** is selected, all users in the team the audience was created in, have edit access to new audiences. (Note: This setting is applied by default). If automatic sharing with the team is disabled, ONLY the creator can see the audience.\n* If automatic sharing is enabled, there’s a sub setting - **notify team members when audience is shared with them\\***.\\* If the option is selected, users will receive an email when new audiences are created.\n\nThe **Audience Sharing** dropdown determines how you can share the audience in the share modal:\n\n* Enable users to share audiences only within their Team (default option)\n* Enable users to share audiences within their Team, and with any user in their Organization as view only\n * **Note:** Sharing an audience with teams or members of teams other than the team the audience was created in, will provide **view only** access to the shared audience.\n\n2. **Sharing an Audience**\n\nHead over to an audience of your choice, and find the \"Share\" option under your Export drop-down menu (top-right):\n\n![](https://files.readme.io/7a1d200-Untitled_1.png)\n\nOnce you click that you're presented with a modal, where you can define who you'd like to share the Audience with and with what permissions:\n\n![](https://files.readme.io/f65329a-image.png)\n\nYou can share audiences and notify users by email (default is to notify), but you can uncheck the checkbox to share without sending the email.\n\n3. **Email Notifications**\n\nOnce notification is enabled, the selected users will receive an email notification when an audience is shared with them.\n\nIn terms of accessibility for this feature, you need to have **editor** access to the audience to share it. For example:\n\n* If audiences are shared with your team when created, all users in the team gain access to the audience and can share the audience, as they are editors.\n* If audiences are not shared with your team when created (this can be established in the org sharing configuration). Only the creator of the audience can see and share the audience. Sharing is an option that will appear in the audience action button (edit, export, delete, share, etc) \n ![Screenshot 2023-09-20 at 1.08.43 PM.png](https://files.readme.io/8f42748-Screenshot_2023-09-20_at_1.08.43_PM.png)\n* If an audience is shared with someone with role **Editor**: the user will be able to share the audience\n* If an audience is shared with someone with role **Viewer**: the user will see the audience, but cannot share it (nor edit, export, delete, etc)\n\nWe hope you get to put this sharing functionality to use and help your team collaborate on audience creation.\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:34.067Z","9db34f3e-cb94-4dc9-8888-9a29f2228889",[],[],{"_40":276,"_128":277,"_130":278,"_132":279,"_134":-5,"_13":-5,"_120":280,"_122":136,"_25":281,"_138":-5,"_139":282,"_141":283},"Audience Snapshotting","audience-snapshotting","https://docs.growthloop.com/docs/audience-snapshotting","Learn how Snapshotting keeps a history of your audiences with every export\n\nDo you know how GrowthLoop helps keep track of your audience changes over time? It’s all thanks to **Snapshotting**.\n\nEvery time you export an audience, GrowthLoop writes a set of snapshot tables to your data warehouse creating a complete history you can query, compare, and use to power insights like [Audience Overlap](https://docs.growthloop.com/docs/audience-comparison#/) and [Audience Evaluation](https://docs.growthloop.com/docs/experiments#/). With Snapshotting, you can:\n\n1. Track when users are added or removed from an audience\n2. Compare audience composition between exports\n3. Unlock GrowthLoop features like Audience Overlap and Audience Evaluation\n\nHere are a few key things to know about how it works and what’s required to use it effectively.\n\n* **Export triggers snapshotting**: When you export an audience, GrowthLoop writes four snapshot tables to the system schema defined in your source connection configuration (commonly named `flywheel_system`, but this may vary based on your setup):\n * **Metadata**: General info about the snapshot run\n * **Snapshot History**: Full audience state at the time of export\n * **Delta History**: Adds/removes since the last export\n * **Unloaded Deltas**: Log of runs written to cloud storage\n* **Full or Incremental updates**: For any destination, you can choose whether to:\n * Export the full audience every time\n * Export only incremental changes (adds/removes) since the last export\n* **Pre-snapshot checks**: Before writing to your warehouse, GrowthLoop runs data integrity checks to ensure there are no duplicates or null values in your primary key.\n* **Exports only**: Snapshots are only created when an audience is exported. If you save or update an audience without exporting it, no snapshot tables will be written. This helps control data warehousing costs by avoiding unnecessary storage.\n* **Warehouse requirements**: Snapshotting requires that your data warehouse connection is active and properly configured, with a system schema defined and GrowthLoop having read/write access. This applies to all supported data warehouses.\n\nNow that you know the key details about how Snapshotting works, let’s take a closer look at each of the snapshot tables and what data they contain.\n\nWhen Snapshotting runs, it doesn’t just create one table - it gives you four, each with its own job. Think of them as different “angles” on your audience’s history: one for the big picture, one for the fine details, one for just the changes, and one for where things are stored. Let's dive into each one:\n\nA quick reference sheet for the snapshot run. It tells you when it happened, what audience it was for, the primary keys used, and other high-level details.\n\n**Naming Pattern**:\n\n```\nsnapshotting_audience_id_metadata\n```\n\n**Example**:\n\n```\nsnapshotting_audience_535_metadata\n```\n\n**Schema**:\n\n| Field Name | Data Type | Description |\n| --- | --- | --- |\n| \\_created\\_at | Timestamp | Timestamp when the record was created |\n| \\_external\\_run\\_id | String | Unique identifier generated by the client initiating the snapshot |\n| \\_snapshot\\_run\\_id | String | Unique identifier for the snapshot run |\n| \\_key\\_fields | String | Primary key field |\n| \\_key\\_fields\\_hashed | String | Hashed primary key field |\n| \\_export\\_ids | String | The ID for the request that triggered the node evaluation |\n| \\_control\\_percentage | Float | Percentage of the audience assigned to the control group |\n| \\_base\\_query\\_json\\_hashed | String | Hash of the audience’s base query in JSON format |\n\nA full record of the audience at the moment it was exported. Every member, every attribute - this is the complete “frozen in time” view.\n\n**Naming Pattern**:\n\n```\nsnapshotting_audience_id_snapshot_history\n```\n\n**Example**:\n\n```\nsnapshotting_audience_535_snapshot_history\n```\n\n**Schema**:\n\n| Field Name | Data Type | Description |\n| --- | --- | --- |\n| \\_created\\_at | Timestamp | Timestamp for record creation |\n| \\_external\\_run\\_id | String | A unique identifier generated by the client that initiated the snapshot request |\n| \\_snapshot\\_run\\_id | String | A unique identifier for each snapshot run |\n| \\_snap\\_hash | String | Internal hash of the snapshot |\n| \\_row\\_hash | String | Internal hash of the row |\n| \\_json\\_row | String | JSON representation of the row |\n| \\_is\\_control | Boolean | Whether customer is assigned to control group |\n| customer\\_id | String | Customer ID |\n| audience\\_name | String | Name of the audience |\n| audience\\_id | Integer | ID of the audience |\n| flywheel\\_export\\_run\\_id | String | GrowthLoop export run ID |\n| client\\_customer\\_id | String | Client-provided customer ID |\n| external\\_id | String | External ID |\n| customer\\_attribute | String | Custom attribute value |\n| \\_export\\_id | String | Export ID |\n\nThe “what’s new” file. It only shows the changes since the last export like who was added, who was removed - so you can focus on just the updates without scanning the whole audience.\n\n**Naming Pattern**:\n\n```\nsnapshotting_audience_id_delta_history\n```\n\n**Example**:\n\n```\nsnapshotting_audience_535_delta_history\n```\n\n**Schema**:\n\n| Field Name | Data Type | Description |\n| --- | --- | --- |\n| \\_created\\_at | Timestamp | Timestamp for record creation |\n| \\_external\\_run\\_id | String | A unique identifier generated by the client that initiated the snapshot request |\n| \\_snapshot\\_run\\_id | String | A unique identifier for each snapshot run |\n| \\_previous\\_external\\_run\\_id | String | External run ID for the previous snapshot |\n| \\_snap\\_hash | String | Internal hash of the snapshot |\n| \\_json\\_row | String | JSON representation of the row |\n| \\_is\\_control | Boolean | Whether customer is assigned to control group |\n| \\_export\\_id | String | Export ID |\n| customer\\_id | String | Customer ID |\n| audience\\_name | String | Name of the audience |\n| audience\\_id | Integer | ID of the audience |\n| flywheel\\_export\\_run\\_id | String | GrowthLoop export run ID |\n| client\\_customer\\_id | String | Client-provided customer ID |\n| external\\_id | String | External ID |\n| customer\\_attribute | String | Custom attribute value |\n| \\_export\\_id | String | Export ID |\n\nA log of export runs that were written out to your cloud storage. If you ever need to track exactly where a snapshot landed, this is where to look.\n\n**Naming Pattern**:\n\n```\nsnapshotting_audience_[AUDIENCE_ID]_unloaded_deltas\n```\n\n**Example**:\n\n```\nsnapshotting_audience_535_unloaded_deltas\n```\n\n**Schema**:\n\n| Field Name | Data Type | Description |\n| --- | --- | --- |\n| \\_created\\_at | Timestamp | Timestamp when the record was created |\n| \\_external\\_run\\_id | String | Unique identifier generated by the client initiating the snapshot |\n| \\_snapshot\\_run\\_id | String | Unique identifier for the snapshot run |\n| \\_cloud\\_storage\\_uri | String | Location in cloud storage where the data was written |\n| \\_export\\_id | String | Export ID |\n\nYou’ve now got the full picture of what each snapshot table does and how they work together. The best way to get comfortable with them? Start exploring.\n\n* Kick off an export and watch the snapshot tables appear in your `flywheel_system` schema.\n* Take a peek at the data in each table to see how the `Metadata`, `History`, and `Delta` views connect.\n* Try a few quick queries to spot changes, track growth, or confirm that exports ran as expected.\n\nOver time, your snapshot history becomes a powerful record, one you can rely on to answer “what changed, when, and why” for any audience.\n\n \n\n> 📘\n> \n> **Have questions or feedback?**\n> \n> We’d love to hear from you! Reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and we’ll be in touch shortly to help resolve the matter!\n\nUpdated 2 months ago\n\n* * *","2025-10-23T18:21:35.149Z","aea9ee90-fa88-497a-a937-fa7fb320bed6",[],[],{"_40":285,"_128":286,"_130":287,"_132":288,"_134":-5,"_13":-5,"_120":289,"_122":136,"_25":290,"_138":-5,"_139":291,"_141":292},"Audit User Activity | GrowthLoop Docs","audit-user-activity-growthloop-docs","https://docs.growthloop.com/docs/user-activity-audit-logs","In this article you'll learn how to see all activities performed by users in GrowthLoop.\n\nIn this Help Center article, we will walk you through the steps to get you familiarized with the User Activity Audit Logs and how you can have better visibility of actions taken by your users in your GrowthLoop organization.\n\nIn order to see your **User Activity Logs** (UALs), you can navigate to your **Organization** tab (on the left hand menu) and click the **Audit Logs** tab. Once you’re there, you’ll be presented with a table where every row indicates an action by a user. Please note that your organization’s event logs go back 1 year or 365 days.\n\nThe Audit Logs tab is only accessible to the **Admin & Owner** user roles.\n\n![](https://files.readme.io/dfc1c29-audit_logs_sample_screen.png)\n\nLet’s dive through what each element on the table represents and how to best utilize it.\n\n**Search**\n\nTo quickly list all the activities related to a **user** or **resource** (eg, Audience, Journey or Sync) you can put the user email or resource ID in the search bar and filter the list down.\n\n**Filters**\n\nIt is very useful to filter down the audit logs to specific users, actions, and resource types to quickly find what you are looking for.\n\n* **Resource Type**: This is the resource the action was taken upon. Think of items like `Journeys`, `Audiences`, `Syncs`, `Destinations` , `Datasets` , `Teams`.\n* **Action:** This is the action that was taken. Think of actions like `Create`, `Update`, `Delete`, `Disable`, etc.\n* **Start Date:** This filter enables you to look at events after a certain start date.\n* **End Date:** This filter enables you to look at events before a certain end date.\n\nThere are various **Resources Types** on GrowthLoop and respectively multiple actions you can take on each resource. For example, if you’re looking to narrow down on Audience Updates, you can filter your `Resource Type` to `Audience` and your `Action` to `Update`.\n\n![](https://files.readme.io/cc5690a-audit_log_filters.png)\n\n**“View logs” button**\n\nNot all logs have a **View logs** button. However, if an activity encompasses changes to a resource type, then you’ll see the view logs button, which highlights those specific changes.\n\nFor example if an audience was updated such that some filters were removed and others were added, you can click on the view logs and see the list of those changes. In the view logs modal, deleted items are highlighted in **red** and added items in **green.**\n\nThe example below shows that the “name” field of the audience has changed.\n\n![](https://files.readme.io/8872e37-diff_audit_logs.png)\n\nHere are the list of user activities that are currently reported on in the User Activity Log table.\n\n* **Audience / Template**\n * Audience Created\n * Audience Updated\n * Audience Deleted\n * Audience Approved\n * Audience Archived\n\nPlease note that **Templates** are also listed under Audience resource type. So if you’re trying to see changes made to a template, you can use its ID to see those changes.\n\n* **Destination**\n * Destination Created\n * Destination Updated\n * Destination Archived\n* **Export**\n * Export Created\n * Export Enabled\n * Export Disabled\n * Export Run — This is when an export is run manually by a user using the **Run** button. This does not include any programmatically scheduled Audience Exports. If you are looking for a record of every audience export for a given audience you can leverage the **Activity Center**.\n* **Sync**\n * Sync Created\n * Sync Updated\n * Sync Run — only when a sync is **manually run** by the user from the menu. If you are looking for a record of every sync export for a given audience you can leverage the **Activity Center**.\n * Sync Enabled\n * Sync Disabled\n* **Journey**\n * Journey Created\n * Journey Updated\n * Journey Published\n * Journey Stopped\n * Journey Archived\n* **Source Connection**\n * Source Connection Created\n * Source Connection Deleted\n* **Dataset**\n * Dataset Created\n * Dataset Updated\n * Dataset Refreshed\n * Dataset Deleted\n* **Dataset Group**\n * Dataset Group Created\n * Dataset Group Updated\n * Dataset Group Deleted\n* **Membership**\n * User Invited\n * User Updated — (eg, role changes)\n * User Removed\n* **Team**\n * Team Created\n * Team Updated — (eg, name change or requiring approval changes)\n * Team Member Added\n* **Session**\n * User Logged In\n * User Logged Out\n\nAudit logs has been built to give you full visibility into user activities in your organization. If there are additional events you’d like to see or you experience any issues, please reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and we’ll be in-touch shortly to help resolve the matter!\n\nUpdated 5 months ago\n\n* * *","2025-06-20T22:58:46.433Z","72e9b501-3761-4db9-b08d-49aaea81e45f",[],[],{"_40":294,"_128":295,"_130":296,"_132":297,"_134":-5,"_13":-5,"_120":298,"_122":136,"_25":299,"_138":-5,"_139":300,"_141":301},"Build a customer journey with GrowthLoop | GrowthLoop Docs","build-a-customer-journey-with-growthloop-growthloop-docs","https://docs.growthloop.com/docs/build-a-journey","# Build a customer journey with GrowthLoop\n\nWelcome to GrowthLoop’s Journey Builder! In this article, we’ll walk you through the suite of capabilities available in the platform and some helpful hints for designing cohesive, delightful journeys for your customers.\n\nA journey of a thousand steps begins with a single… audience. That’s right, it all loops (GrowthLoops?) right back around to using Audience Builder to create a segment of customers based on the data living in your data warehouse. Learn more about building audiences with GrowthLoop in [this article](https://docs.growthloop.com/docs/create-an-audience).\n\nNavigate to the **Journeys** tab on the left side of your screen.\n\n![](https://files.readme.io/8ee3a51-journeys_navigation.png)\n\nClick **New Journey**.\n\n![](https://files.readme.io/07e43fe-new_journey.png)\n\nAdd a **Journey Name**. A name is required to save your journey.\n\n![](https://files.readme.io/336a9c9-journey_name.png)\n\nYou will now need to complete **Journey Setup** by providing the following information:\n\n**Entry Criteria:** The audience you want to use as the entryway to the journey.\n\n![](https://files.readme.io/dd71261-journey_settings.png)\n\n**Schedule:** You have several options for customizing your journey schedule.\n\n![](https://files.readme.io/2773554-journey_schedule.png)\n\n1. **Journey Schedule:** Choose your journey schedule type.\n 1. **One Time:** Run this journey one time only, either upon publish or at a specified time.\n 2. **Always On**: Keep this journey running continuously from my specified start to end times. **Never** is an end time option for a journey you wish to run indefinitely.\n 3. **Recurring Scheduled:** Run this journey intermittently based on my desired schedule. You can identify the day(s) of the week and time(s) when you wish for your journey to run. As with **Always On,** you are required to specify start and end times.\n\n**Additional Settings:** You have a few additional configuration options, including **Journey Re-entry.** This feature allows you to declare whether individuals who exit the journey are allowed to re-enter the journey if they again meet the entry criteria. If you want to allow re-entry, you will be asked to specify how long an individual must wait between exiting and re-entering the journey. This time can be zero if you want them to immediately re-enter.\n\n![](https://files.readme.io/5eb01d2-journey_additional_settings.png)\n\nClick **Continue.**\n\nYou are now able to build your journey on the journey canvas!\n\n**Navigating the Canvas**\n\nTo navigate around the canvas, click and drag anywhere on the screen. As you build your journey, you will be able to see the high-level structure in the **Mini Map** on the right side of the screen. You can also adjust your **Zoom** using the controls below the Mini Map.\n\n![](https://files.readme.io/d2541ca-Setup_journey.gif)\n\nWith these controls in mind, you are now able to build your customer journey using any combination of the five node types (described below) shown on the **Library** on the right side of your screen.\n\n![](https://files.readme.io/746d3df-journey_node_library.png)\n\nYou can add a **Node** to your journey by clicking and dragging it from this menu onto the journey canvas. To connect nodes in your desired progression, click the circle on the bottom edge of the “parent” node and drag it to anywhere along the top edge of the “child” node.\n\nYou can rename any of the nodes on the canvas by double-clicking on the header and entering your desired text.\n\n**Entry Node**\n\nEvery journey starts with an **Entry Node** identifying the audience that is used as the gateway to the journey. This is the audience you specified during the **Journey Setup** stage.\n\n![](https://files.readme.io/bf5188d-journey_entry_node.png)\n\n**Criteria Node**\n\nA criteria node (also called **group criteria node**) allows you to build mini-audiences into as many groups as you need in your journey.\n\nThe criteria node starts with 1 grouping + everyone else. This means any users who flow into the criteria node, will be first assessed against the conditions you set on Group A and if they don't meet those criteria, they're passed through the \"Everyone Else\" path.\n\n![](https://files.readme.io/f74a9093b0f24e2282513b0167590f006a72be42b3c6d876a475b7e5738183d5-image.png)\n\nYou also have the ability add as many groupings as you'd like. In this case users flowing into the criteria node, will be assessed based on the rules set in the nodes **from left to right** (ie, checked against your criteria in Group A and if they don't meet them, they move to Group B's criteria and so on in a waterfall manner).\n\n![](https://files.readme.io/92171d7cef1bc093f6ac7a9243fd8292d86bb993820931063d413c50be2e16fd-image.png)\n\nIf you ever need to change the order of your grouping, you can hover over each group and you'll see the mini left/right arrow (image above). Clicking them will move the grouping to the left or right respectively.\n\nNow let's get into how you can define your criteria inside a single group.\n\nA criteria node is essentially a mini-audience Builder that allows you to filter members of your audience across any table you’ve connected from your data warehouse. To add a criteria, double click on the **Select Criteria** option. By default, the criteria builder will prompt you to add a filter from your customer table. You can select filters from other tables by clicking **Transactions** or **Events** and selecting your desired dataset. In addition to adding filters, you can further customize the appearance of the criteria builder by adding elements like **Headings**, **Text,** and **Sections.**\n\n![](https://files.readme.io/71c2e96-journey_criteria_node.gif)\n\nIn addition, the criteria node includes an **Evaluation** feature, which gives you more control over how and when the criteria are evaluated:\n\n![](https://files.readme.io/16a86854e608f92dbfff9a68e6efb0b8208ecf87a1ce0123ee02753b72f84286-image.png)\n\n* **Evaluation Step Once On Entry** (default): Members are evaluated as soon as they enter this group in the criteria node, and they move down this criteria path if they meet them. If they do not, they proceed down to the next grouping in your group criteria node.\n* **Set Evaluation Window**: Members are evaluated regularly over a specified window of days or hours. As soon as they meet the criteria, they meet this group's criteria and proceed down the journey. If they do not, they proceed down the remaining groups of your group criteria node.\n* **Limit (optional)**: You can also set a limit on the number of users that meet the criteria and sort them by a user property in ascending or descending order.\n\nThis flexibility ensures that audience members have adequate time to meet the criteria before moving forward and you can further limit the number of users that pass through based on your specific sorting.\n\n![](https://files.readme.io/46d374385c42ef611fbd7c0a1eb5cebe8f4fa8e4f77b46fd677a5b76abe7fe3d-image.png)\n\nBelow we're sorting users that meet our criteria by the total number of purchases (in descending order) and only picking the top 5 users.\n\n![](https://files.readme.io/644510e4565eb23cc961b72cc452a1d8a816f9fc7c4a49d7361f0e15717707a2-image.png)\n\nWhen you are finished configuring your criteria node, click apply or anywhere outside the criteria builder and you will be brought back to the journey canvas. You can rename your criteria node to reflect this filtering stage by double-clicking **Criteria** and adding your title text.\n\nOnce this node is complete, your audience will be segmented into as many groupings as you have in the group criteria node. This allows you to send each group down their respective sub-branch in the journey as indicated below.\n\n![](https://files.readme.io/861a16560a38e2efb5847e755247803afc37d58fd5a850627040d62bfb449d95-image.png)\n\n**Delay Node**\n\nA delay node is used to add a time buffer between nodes. For instance, if you send an audience a discount offer via email and want to check for a conversion after sending, you will want to introduce some kind of time interval to allow the desired purchase to occur.\n\nThe delay node looks simple upon first glance - the **Basic** option shown on the node prompts you to specify a single interval of time to separate the preceding and succeeding nodes.\n\n![](https://files.readme.io/5fb533b-journey_delay_node.png)\n\nTo obtain **delay options** double-click on the node. You now have the option of setting and configuring one of the following **Delay Types.**\n\n![](https://files.readme.io/ce763d9-journey_advanced_delay_options.png)\n\n1. **Certain Amount of Time**: Advance individuals to the next node only once a specific period of time has elapsed after they advance from the prior node (i.e. one day).\n2. **Until an Exact Date/Time:** Advance individuals to the next node only at a certain date/time (i.e. only on September 13th at 9 AM).\n3. **Until a Specific Day of the Week:** Advance individuals to the next node on a recurring basis (i.e. Wednesdays at 4 PM).\n\n**Destination Node**\n\nA destination node allows you to send members of your journey to a specific destination. Available destinations are a subset of those currently offered for GrowthLoop’s Audience Builder.\n\nClick **Select a Destination** and choose your desired platform. Once you have chosen your platform, you will need to configure your export by providing several pieces of information.\n\n![](https://files.readme.io/fd8d891-destination_node.png)\n\n1. **Export Name**: How to identify this subset of journey members in your destination platform and in GrowthLoop export logs.\n2. **Match Fields:** How to match customer records from this audience to individuals in the destination platform. Only required for certain destinations.\n3. **Personalization Signals:** Which signals to send with your audience members to the destination platform. Only available for certain destinations.\n\nOnce you have completed all required/desired fields, click **Save.**\n\n**Experiment Node**\n\nThe experiment node allows you to split your journey members into an unlimited number of randomized groups for experimentation. The group assignment of all individuals will be written back to your data warehouse to enable custom analytics by your team.\n\nYou can split your experiments **by % or count.**\n\n![](https://files.readme.io/dec18424b33b7bb24d8b18e9f040ef93a91fa9639e9f6ae356f9474bfe6a2ca3-image.png)\n\n**Experiments by %** Add as many groups as needed to support your experiment by clicking the **+** icon. You can provide each group with a name by double-clicking on the **Variation** text for the group.\n\nFor each group, identify what % of the audience should be randomly assigned to each group. Note that the total of these percentages **must add up to 100%**, or you will receive an error.\n\n![](https://files.readme.io/0311bbb-experiment_node.png)\n\nTo send each group down a particular pathway, click the circle at the bottom edge of the group’s box and drag it down to the next step in their journey. Note that all groups can ultimately be brought back together by merging them into a single journey step once the experiment you are interested in (i.e. testing the effectiveness of different destination platforms) has been completed.\n\n![](https://files.readme.io/0bcce49-experiment_path.png)\n\n**Experiments by count** In this case users flowing into the experiment node will be grouped from left to right.\n\n![](https://files.readme.io/97dbf5e0db7cea43c6a9985310ead7ba2502d441a2284d858969c2fd00d42f6e-image.png)\n\nIf 10,000 users were to flow into the experiment node above, the first 2,000 go through Var 1, the next 1,000 to Var 2, the next 500 to Var 3 and all the remaining 6,500 through the last variation.\n\nThis allows you to control the absolute number of people that flow through each experiment vs. a randomized splitting.\n\nIn order to preserve your latest changes, you **must click Save.**\n\n![](https://files.readme.io/2d9b881-save_journey.png)\n\nOnce your journey has been saved, it is eligible to be **Published.** Publishing a journey means that you are allowing it to be activated according to the schedule set by your journey settings.\n\n![](https://files.readme.io/9d0cce1-publishing_journey.png)\n\nIf you want to modify your journey schedule and additional settings, you can click the **Settings** tab at the top of the Journeys canvas.\n\n![](https://files.readme.io/f09822c-view_journey_settings.png)\n\nFor more information or to provide feedback to the team, please reach out to [support@growthloop.com](mailto:support@growthloop.com.). We can’t wait to hear from you!","2024-03-20T21:02:34.651Z","7e74b581-2f95-481f-8fc1-332d6351321e",[],[],{"_40":303,"_128":304,"_130":305,"_132":306,"_134":-5,"_13":-5,"_120":307,"_122":136,"_25":308,"_138":-5,"_139":309,"_141":310},"Build audiences using SQL | GrowthLoop Docs","build-audiences-using-sql-growthloop-docs","https://docs.growthloop.com/docs/build-audience-with-sql","## Create an Audience with SQL\n\nHow to build an audience using SQL\n\nThe fastest way to build an audience is through our [Visual Audience Builder](https://docs.growthloop.com/docs/create-an-audience) or [Marve Studio](https://docs.growthloop.com/docs/marve), our AI Audience Assistant. However, sometimes you just want to use SQL. Well, we support that too.\n\nHere is a quick walk through of how to build an audience with SQL in GrowthLoop.\n\n1. Click Models on Left Hand Menu. Provide your Model Name.\n2. Write SQL for your audience. You can use any tables accessible in your Data Cloud `Source Connection`. Click `Save Model.`\n\n![](https://files.readme.io/e61c76e2d3f0d37832b8edae31fc9a918f61199fc6ba91a3b69edeeb56e0e723-audience_withsql.png)\n\n3. Connect your Model to a `Dataset`.\n \n 1. Click `Datasets` in Left Hand Menu. Click `Dataset` tab. Then click `New Dataset`.\n 2. Select `Is Primary Dataset`. Select Dataset Source Type `SQL Model`. Select your `Model`. Then scroll and select `Create`.\n \n ![](https://files.readme.io/550f5d5b9801c06a360b5c9cec601bdc4ebe789190c422f146cedf2c1d7eeff3-Datasetsetup.png)\n4. Add to a `Dataset Group`. This registers your audience to be exported.\n \n 1. Click `New Dataset Group`.\n 2. Provide `Group Name`. Select `Dataset` you just created. Click `Create`\n5. Click `Audiences` in left hand menu. Click `New Audience`. Select the newly created `Dataset Group`.\n \n6. Give your audience a name and click `Export`\n \n\n![](https://files.readme.io/9434a8bb86f3688ce6da184145b88087fd0dead6c6df581d4219fe24ca9cf4ef-audiencecanvassql.png)\n\n7. Export your audience to any `Destination` connected to GrowthLoop.\n\n![](https://files.readme.io/60218e6a4780da1f2608499b503dbbb15346b12edfd4c698f8ee921e6b6a9691-exportaudiences.png)\n\nIf you have any questions about setting up your SQL based audience please contact [support@growthloop.com](mailto:support@growthloop.com).\n\nUpdated 5 months ago\n\n* * *\n\n* [Create an Audience](https://docs.growthloop.com/docs/create-an-audience)\n* [Marve Studio](https://docs.growthloop.com/docs/marve)","2025-06-20T22:58:08.131Z","99f51fd4-f68c-4748-94f5-8aab108d39ca",[],[],{"_40":312,"_128":313,"_130":314,"_132":315,"_134":-5,"_13":-5,"_120":316,"_122":136,"_25":317,"_138":-5,"_139":318,"_141":319},"Capture and target anonymous web visitors | GrowthLoop Docs","capture-and-target-anonymous-web-visitors-growthloop-docs","https://docs.growthloop.com/docs/anonymous-audience-export-to-meta-facebook","# Capture and target anonymous web visitors\n\n## Facebook Ads Anonymous ID\n\nIn this document we’ll walk you through how GrowthLoop can enable your organization to capture your **anonymous** website visitors, help you build audiences around them to be exported to Meta (Facebook) for better targeting.\n\nThis is possible through GrowthLoop’s partnership with [MetaRouter](https://www.metarouter.io/).\n\nThe first step to be able to build audiences based on your anonymous visitors is setting up MetaRouter on your website and/or application.\n\nThis step allows user activities (eg, page views, clicks…etc) to be captured and piped into your data warehouse such as BigQuery, Snowflake, Databricks and others.\n\nThe details and steps for the setup are documented [here](https://docs.metarouter.io/docs/getting-started-with-metarouter), however, the MetaRouter and GrowthLoop team are here to help you get set up and started.\n\nOnce your anonymous user data starts flowing into your data warehouse, you need to start consolidating the data on how you intend to utilize that.\n\nFor your specific setup the GrowthLoop team is here to help you get started. But in short, we help you bring all **events** and **anonymous user** data under their own umbrellas, so you can easily build GrowthLoop Datasets off of them and filter your audiences accordingly.\n\n‍\n\nBefore you meet our team at GrowthLoop for your specific set up, we’d require you to please have your **Pixel ID** ready from your Facebook account.\n\nIf you don’t have a **Pixel ID** yet, you can create one [using Meta’s instructions here](https://www.facebook.com/business/help/314143995668266?id=1205376682832142). And if you do have one set up, you should be able to get it by logging into your **Facebook Ad Manager —> Events Manager** ([more details here](https://www.facebook.com/business/help/898185560232180?id=1205376682832142))**.**\n\nOnce the above is set up, you need to set up your **destination** on GrowthLoop. Head over the **Destinations** menu (on the left-hand side) and click **New Destination.** You can then search for **Facebook Conversions** to get the following destination:\n\n![](https://assets-global.website-files.com/6452937893cd845b6181c39e/65afe76a35e66222dac075ab_Screenshot%202024-01-23%20at%2011.20.16%20AM.png)\n\nOnce you click the card, you’re asked to log into your Meta/Facebook account. And after getting authenticated, you’re provided with the following connection form.\n\n**Note:** It’s important that you **include your Facebook Pixel ID** in the **FB Pixel** field for this connection to work.\n\n![](https://assets-global.website-files.com/6452937893cd845b6181c39e/65afe77c184c39624d556523_Screenshot%202024-01-23%20at%2011.20.26%20AM.png)\n\nOnce you’ve successfully set up your destination, you can start building your audience on top of the Datasets that were defined earlier and export to the newly established destination above.\n\nYou need to export an audience (preferably a test one) in order to verify and accept the event GrowthLoop uses to send your audiences under, to Meta/Facebook. In order to do that, create an audience on GrowthLoop and export using the newly created destination.\n\nYou need to **wait for approximately 1 hour** after you export your audience and log back into Facebook’s business account, to see a **new event**. GrowthLoop names this event **Audience Membership**. So if you see that event under the list of your events, go ahead and **verify & accept it.**\n\nAt this point you’re all set and you can use Facebook/Meta’s Audience creator, based on the newly verified Event on the FB advertising platform.\n\nIf you experience any issues or have any questions, please reach out to us at [support@growthloop.com](mailto:support@growthloop.com), and we’ll be in touch shortly!\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:39.187Z","c858840b-b308-41d9-8e01-9f897d06909a",[],[],{"_40":321,"_128":322,"_130":323,"_132":324,"_134":-5,"_13":-5,"_120":325,"_122":136,"_25":326,"_138":-5,"_139":327,"_141":328},"Check the health of your audiences for marketing campaigns | GrowthLoop Docs","check-the-health-of-your-audiences-for-marketing-campaigns-growthloop-docs","https://docs.growthloop.com/docs/health-checks","# Check the health of your audiences for marketing campaigns\n\n## Health Checks\n\nLearn how to monitor the freshness and reliability of your data in GrowthLoop.\n\nAs a marketer, the accuracy and freshness of your data is **crucial** - it’s what powers effective segmentation, personalization, and campaign timing. Unfortunately, more often than we’d like, the data you rely on is stale or incomplete, and you don’t find out until it’s too late. The impact? Wasted budget, missed opportunities, and silent campaign failures.\n\nHere are a few common nightmare scenarios:\n\n1. **Paid Media Waste**: Imagine you’re using a customer list to suppress existing customers from receiving ads. If that list hasn’t updated in 7 days, you’re wasting ad dollars showing ads to people who became customers a week ago.\n2. **Missing the Moment**: You’re trying to cross-sell based on a customer’s recent purchase. But if the purchase data hasn’t updated in days, you miss the critical window when the customer is most likely to engage.\n3. **Silent Campaign Failures**: What if your onboarding or triggered campaigns rely on a dataset that suddenly stops updating—and no one tells you? You only find out days later when emails stop sending and you have to scramble to diagnose the issue.\n\nIf you’ve been in marketing long enough, you've probably experienced one (or more!) of these. But here's the good news - **these are all avoidable**.\n\nThat’s why we built **GrowthLoop Health Checks** - think of it as a data insurance policy for marketing teams. GrowthLoop continuously monitors every dataset connected to your account and automatically keeps an eye on every live audience export. If any dataset stops updating or gets dropped, you’ll be proactively notified, so you can take action before your campaigns are impacted.\n\n* GrowthLoop monitors all connected datasets in your Data Cloud for updates.\n* Any live, exporting audience relying on those datasets is also monitored.\n* If a dataset stops updating, both the dataset owner and audience owner will be notified.\n* This keeps Data teams and Marketing teams aligned, ensuring your campaigns run on fresh, reliable data.\n\n![](https://files.readme.io/3eb944c-health_checks_diagram.png)\n\n1. Navigate to the **Datasets** Page.\n2. Click the **Datasets** Tab.\n3. Search for the dataset you want to check.\n4. Scroll right to view the **Last Updated** date and **Status**.\n5. Status colors: \n 🟢 **Green**: Updated within the last 24 hours. \n 🟡 **Yellow**: Updated within the last 72 hours. \n 🔴 **Red**: No updates in over 7 days.\n\n1. Go to **Audiences**.\n2. Click **New Audience** or choose an existing one.\n3. On the individual audience page, click the **Health** tab on the right-hand side.\n4. You’ll see the health of underlying datasets: \n 🟢 **Green**: Updated within 24 hours. \n 🟡 **Yellow**: No updates in 72 hours - check with the table owner. \n 🔴 **Red**: No updates in 7+ days - check before using.\n\n1. Click **Organization** in the left menu.\n2. Go to the **Notifications** tab.\n3. Add users/emails under **Dataset Update Failure**.\n4. Click **Save**.\n\nWith **GrowthLoop Health Checks**, you can rest easy knowing your campaigns are backed by fresh, reliable data. No more wasted spend, no more scrambling to diagnose silent failures - just accurate, up-to-date data driving your marketing success.\n\n> 📘\n> \n> If you experience any issues, please reach out to us at [support@growthloop.com](mailto:support@growthloop.com), and we’ll be in touch shortly to help resolve the matter!\n\nUpdated 5 months ago\n\n* * *","2025-06-20T22:58:15.612Z","0c5141a3-37f7-4778-b7fc-0d6bc71aa453",[],[],{"_40":330,"_128":331,"_130":332,"_132":333,"_134":-5,"_13":-5,"_120":334,"_122":136,"_25":335,"_138":-5,"_139":336,"_141":337},"Community","community","https://docs.growthloop.com/docs/community","You can now export audiences from your Data Warehouse to Community for SMS customer engagement.\n\nIn this Help Center article, we will walk you through the steps to get **Community** connected as a destination in the GrowthLoop web application. Once connected, you will be able to send your audience segments to Community for SMS customer engagement!\n\n* Before you begin this process, you must have a Community account. If you don’t, please click [here](https://www.community.com/get-a-number) to book a demo with a Community representative.\n\n1. When you sign into the GrowthLoop platform, navigate to the **Destinations** tab on the left sidebar and click **New Destination** in the top right corner.\n\n![](https://files.readme.io/a6a36d7-Untitled.png)\n\n2. When the **Select Destination** window pops up, type **Community** into the search bar and click **Add Community**.\n\n![](https://files.readme.io/4ee03bd-Untitled_1.png)\n\n3. Clicking **Add Community** will require you to select/insert the following information:\n\n![](https://files.readme.io/9d1dd25-Untitled_2.png)\n\nDestination Info:\n\n* **Destination Name:** This is how the destination will be named and referred to in to the app going forward. It is helpful to make this name “marketer friendly” so everyone on your team knows its purpose.\n* **Sync frequency**: This is the default frequency audiences will be synced to a destination. Marketers can always change frequency of an export, but this sets the default.\n\nCredentials:\n\n> 📘\n> \n> To view the account's settings page with the Client ID and Auth Token, log in to your Community account.\n\n* **Client ID**: A unique identifier that is used to authenticate and authorize API calls. To locate it, go to [https://dashboard.community.com/settings/api-tokens](http://dashboard.community.com/settings/api-tokens).\n \n* **Auth Token**: Unique string that serves as a credential for authentication and authorization purposes. To generate it, go to [https://dashboard.community.com/settings/api-tokens](http://dashboard.community.com/settings/api-tokens) and click Generate New Token.\n \n ![](https://files.readme.io/aa4e207-image.png)\n \n\n4. Go ahead and select **Create**, and we’ll validate we have all the proper permissions to load audience data. You should now see Community in your list of connected destinations!\n \n ![](https://files.readme.io/2df8e82-Untitled_3.png)\n\n5. To export an audience, you’ll need to build one first. Click **New Audience** and [Create your New Audience](https://www.growthloop.com/help-center-articles/create-an-audience).\n\n![](https://files.readme.io/f13e944-Untitled_4.png)\n\n6. Once you finish building the audience, click **Export Audience**.\n\n![](https://files.readme.io/4d43c98-Untitled_5.png)\n\n7. When the **Create Export** window pops up, type **Community** into the search bar and click **Select**.\n\n![](https://files.readme.io/8609979-Untitled_6.png)\n\n8. Then in the **Export Settings** tab, configure your desired **Export Name**, **Campaign Type** and **Export Schedule.** By default, the name field will auto populate to your audience name so you can easily find it in your destination.\n\n![](https://files.readme.io/eedd0a5-Untitled_7.png)\n\n9. Next, set up your match fields in the **Match Fields** tab. Mapping **Phone**, **Date of Birth**, and **State** is mandatory for the export process. Ensure they are in the correct format:\n 1. **Phone**: XXX-XXX-XXXX\n 2. **Date of Birth**: YYYY-MM-DD\n 3. **State**: Full name (e.g., California) or Abbreviation (e.g., CA)\n\n![](https://files.readme.io/62e107c-Untitled_8.png)\n\n10. Lastly, click **Export**, and you're done! Congrats on successfully exporting an audience to Community. To view it, login to your [Community](https://dashboard.community.com/communities) account and navigate to the **Communities** page.\n\n![](https://files.readme.io/8e8a1d0-Untitled_9.png)\n\nExperiencing any issues when connecting to **Community**? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and we’ll be in-touch shortly to help resolve the matter!\n\nUpdated 5 months ago\n\n* * *","2024-04-10T18:41:36.642Z","2cde31eb-99c8-4dc5-ab89-4b78816d0fc7",[],[],{"_40":339,"_128":340,"_130":341,"_132":342,"_134":-5,"_13":-5,"_120":343,"_122":136,"_25":344,"_138":-5,"_139":345,"_141":346},"Comparing and Excluding Audiences","comparing-and-excluding-audiences","https://docs.growthloop.com/docs/comparing-and-excluding-audiences","Comparing and Excluding Audiences\nThis article outlines the steps necessary to use Audience Comparisons to identify pre-existing Audiences that overlap with your current audience criteria. This will also cover selecting an audience to be excluded from your criteria.\nSelect Audiences from the left rail of your GrowthLoop home screen. Click New Audience on the top right. Select the build option you would like to use. For this example, we used Marve to build an audience using a prompt.\nGive your Audience a name. Add any additional filters to further narrow down your audience segmentation. In the right hand frame, select the Comparisons tab. The Top Overlap Audiences section will load automatically and present audiences in the order of most overlap to least overlap.\nThe color-code numeric % values next to each audience, indicate that you have previously created a similar audience with this criteria. This is to help you prevent targeting the same audience with similar campaigns and be more efficient with your budgets. \nRed - High: Greater than 66% overlap\nYellow - Medium: Between 33% and 66% overlap\nGreen - Low: Less than 33% overlap\nFor this example, it could be a good idea to exclude users that are in the High Churn Risk audience. The audience has only 30% overlap indicated in green. We might be using that audience in a separate journey or campaign that is active and trying to drive re-engagement. To exclude this audience, click the audience name and select Exclude.\nThe audience will now appear in the criteria list at the top with where not automatically applied.\nTo pin an audience to the top of the Comparisons section for ongoing evaluation, click the audience name from the Overlap List and select Add as target audience.\nAny audiences that you have added as Target Audiences will appear as tiles with overlap % and customer count.\nClick the Ellipsis at the top right of an audience tile to Exclude the audience from the current audience build. The audience can also be Removed from the pinned audience section.\nIf you experience any issues, please reach out to us at solutions@growthloop.com, and we’ll be in touch shortly to help resolve the matter!\nUpdated 3 months ago","2024-03-20T21:02:33.614Z","820d1ab1-c1fc-4b02-b5f0-615e4e292fc0",[],[],{"_40":348,"_128":349,"_130":350,"_132":351,"_134":-5,"_13":-5,"_120":352,"_122":136,"_25":353,"_138":-5,"_139":354,"_141":355},"Configure audience exports to Salesforce | GrowthLoop Docs","configure-audience-exports-to-salesforce-growthloop-docs","https://docs.growthloop.com/docs/configuring-audience-exports-to-salesforce","# Configure audience exports to Salesforce\n\n## Configuring Audience Exports to Salesforce\n\nWhen you go to export an audience to Salesforce, you can specify how GrowthLoop should match audience members to your Salesforce leads, contacts and accounts. Each match condition unlocks a different set of actions to apply to matching and non-matching profiles in Salesforce.\n\n**Match on Contacts and Leads:** Look for matches across all contacts and leads in Salesforce.\n\n**Match on Account:** Look for matches with accounts in Salesforce.\n\n**Match on Leads Only:** Look for matches only with Salesforce leads, ignoring contacts.\n\n**Create Campaign in Salesforce for each GrowthLoop Audience:** Selecting **Yes** will create a campaign for this audience in your Salesforce instance. To do so, you must have **Marketing User Privileges** assigned to your Salesforce username.\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd84dd7181ca8e_Untitled.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd84dd7181ca8e_Untitled.png)\n\nWhen matching on contacts and leads, you have an extensive set of options for customizing your audience export to Salesforce.\n\n**Matching Contacts**\n\nYou can filter all contact matches across opportunity type, owner, and stage, applying a specific action to only contacts who meet these criteria. Available actions include adding tasks, opportunities, and activities. You have the option of assigning this action to either the opportunity owner (by checking **Copy opportunity owner for this task**) or specifying a different owner’s email address.\n\nYou can also choose a separate action to apply to matching contacts who _do not_ meet your opportunity criteria.\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd849a2a81ca8c_Untitled.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd849a2a81ca8c_Untitled.png)\n\n**Matching Leads**\n\nAs with contacts, there are a variety of actions available for matching leads, ranging from updating the lead to converting it to an account and contact.\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd84684081ca95_Untitled.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd84684081ca95_Untitled.png)\n\n**Non-Matching Contacts or Leads**\n\nFinally, you can also action on any audience member who _does not_ match an existing contact or lead in Salesforce. You can create a new lead or a new contact (among others) by identifying the fields in your data that correspond with an individual’s company, name and contact information.\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd8426e481ca9b_Untitled.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd8426e481ca9b_Untitled.png)\n\n**Choosing Match Fields**\n\nFinally, choose the data identifier that will match your GrowthLoop audience members to your Salesforce leads and contacts. This is typically a Contact ID or email address.\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd8493c081ca94_Untitled.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd8493c081ca94_Untitled.png)\n\nSelecting “Match on Account” allows you to match on Salesforce account, rather than contact or lead. As with contacts and leads, you can apply actions to accounts right from GrowthLoop!\n\n**Matching Accounts**\n\nYou can filter all account matches across opportunity type, owner, and stage, applying a specific action to only accounts that meet these criteria. Available actions include adding tasks, opportunities, and activities. You have the option of assigning this action to either the opportunity owner (by checking **Copy opportunity owner for this task**) or specifying a different owner’s email address.\n\nYou can also choose a separate action to apply to any contacts who _do not_ match your criteria.\n\nSelecting “Match on Leads Only” allows you to match audience members to Salesforce leads only, ignoring Salesforce contacts.\n\n**Matching Leads**\n\nFor matching leads, you can add a task, convert the lead and create an opportunity, or do nothing.\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd840dbd81ca96_Untitled.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd840dbd81ca96_Untitled.png)\n\n**Non-Matching Leads**\n\nFor audience members that do not match an existing lead, you can create new Salesforce leads or contacts by specifying the fields in your data that correspond with members’ companies, names and contact information.\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd84192d81ca97_Untitled.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd84192d81ca97_Untitled.png)\n\n**Non-Matching Leads**\n\nFor audience members that do not match an existing lead, you can create new Salesforce leads or contacts by specifying the fields in your data that correspond with members’ companies, names and contact information.\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:34.209Z","c2f57500-68a9-4bb7-900f-abbf7b3b0bba",[],[],{"_40":357,"_128":358,"_130":359,"_132":360,"_134":-5,"_13":-5,"_120":361,"_122":136,"_25":362,"_138":-5,"_139":363,"_141":364},"Configure your data and create a dataset | GrowthLoop Docs","configure-your-data-and-create-a-dataset-growthloop-docs","https://docs.growthloop.com/docs/setup-datasets","# Configure your data and create a dataset\n\n## Set Up Datasets\n\nLearn how to configure your data in GrowthLoop\n\nIn this article, you'll configure your first `Dataset` in GrowthLoop. Adding a dataset takes seconds to begin using for activation. We'll walk through each step together.\n\n![](https://files.readme.io/31da97a4d9d5b646a3b4c12a2f1aa8627450f6e4066490d7d581bfeb819fd9d5-image.png)\n\n1. Navigate to `Datasets` in the left menu rail\n2. Select the `Datasets`tab. Here you can see all `Datasets` your team has connected to GrowthLoop\n3. Select `New Dataset`\n4. Select your `Dataset Type`\n5. Select the data source type`Table or View` or `Model`\n6. Select the`Dataset`where your table exists in your source connection\n7. Select the `Table`you want to reference\n8. **Provide Table Alias:** Table aliases will appear in the Audience and Journey builders to make it easier for others to recognize and use your `Dataset`. We recommend putting in a name others in your organization will recognize.\n9. **Add Table Description:** Insert a table description so others on your team will know what type of data they can find and use in this `Dataset` when creating Audiences and Journeys.\n10. Select `Unique Key`. We will check your table to ensure your key is unique.\n\n![](https://files.readme.io/96ba5e2-check_unique_key.png)\n\n> 📘\n> \n> If your table does not have a unique key, you can use a Composite Key. You can select multiple fields on your table. Our platform will append those fields and check if the composite key is unique to every record on your table. This is a great way to leverage our platform even when you do not have a single unique column on a table.\n\n1. **Dataset filters**\n \n 1. If you only want to expose a sub-set of the data in your dataset, you can further filter down your dataset.\n \n ![](https://files.readme.io/f9e881b50db5447d92f4298a73cd099c44b0155b04cbee1939b712c8bd0b69fc-image.png)\n \n 2. Above we have filtered down the dataset to those who have their **state = Arkansas** and by hitting the preview button you can see a sample records of those filtered data.\n \n2. **Configure fields**: Configure the fields in your dataset.\n \n 1. **Type**: This shows the data type of the column that we detected for your `Dataset`. This is detected directly from your source schema.\n 2. **Show by Default**: Select fields you will want to show up in the Audience Builder and Journey Canvas when a user selects targeting. All fields will be available from your `Dataset`, but the fields designate as `Show by default` will appear on the page, always making them more accessible to users.\n\n![](https://files.readme.io/6d3f6d4-Screenshot_2024-01-23_at_2.00.42_PM.png)\n\n3. **[Tag PII Fields](https://dash.readme.com/project/growthloop/v1.0/docs/pii-management):** Protect certain columns from being viewed in platform.\n 1. GrowthLoop blocks **PII Fields** from appearing as filters in your Audience Builder.\n 2. Tagging columns as **PII Fields** also prevents users from downloading any CSVs with this data.\n 3. \\*Note:\\***PII Fields** can still be used as personalization signals that are sent to marketing destinations to personalize messages. To restrict this ability, you should **Exclude from Personalization**.\n4. **Exclude from Personalization**: You can exclude fields from being used as personalization in exports. Users will not be able to add these as fields for audience exports. This is valuable if there is certain data, like revenue, you do not want going to any marketing destinations or CSV.\n\n![](https://files.readme.io/c3dd02b-pii_fields.png)\n\n5. **Label**: Label the fields in your `Datasets` so they are easier to use in the application for your team. This helps your team know what type of data is in each column and unlocks `Recipes` for your team to use in the platform. More details on [Recipes can be found here](https://dash.readme.com/project/growthloop/v1.0/docs/audience-recipes-templates).\n\n![](https://files.readme.io/3876cdd-dataset_labels.png)\n\n* * *\n\n> 👍\n\nYour dataset can now be used to create:\n\n* [Overview](https://docs.growthloop.com/docs/syncs-overview) Must add your dataset to a specific `Dataset Group`\n* [Audiences:](https://docs.growthloop.com/docs/audiences-overview) Must add your dataset to a specific `Dataset Group`\n* [Journeys:](https://docs.growthloop.com/docs/experiments) Must add your dataset to a specific `Dataset Group`\n\nIf you are experiencing any issues with GrowthLoop? Reach out to us at **[support@growthloop.com](mailto:support@growthloop.com)** and we’ll be in touch shortly!\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:23.417Z","840b24d3-596b-4e92-ba65-b1e38b383659",[],[],{"_40":366,"_128":367,"_130":368,"_132":369,"_134":-5,"_13":-5,"_120":370,"_122":371,"_25":372,"_138":-5,"_139":373,"_141":374},"Connecting SQL Server to GrowthLoop","connecting-sql-server-to-growthloop","https:/","To connect your SQL Server to GrowthLoop, follow these steps:\n\n1. Navigate to the Source Connection Management page in GrowthLoop. You can find detailed instructions in the [documentation](https://docs.growthloop.com/docs/source-connection-management) or directly access the page in the app under the Organization tab in settings: [Source Connections](https://app.flywheelsoftware.com/organization?state=source-connections).\n\n2. Select SQL Server as the source connection type.\n\n3. Enter the required credentials and connection information. This information is typically available in the \"Connection strings\" tab of your SQL database management page in Azure.\n\n4. If your server restricts traffic to specific IP addresses, whitelist the following GrowthLoop IPs:\n - 34.69.50.194\n - 35.226.252.61\n - 34.121.106.121\n - 35.239.73.167\n\n5. After establishing the connection, create a new dataset referencing the desired tables from the SQL Server source connection.\n\n6. Set up a new Dataset Group to organize and utilize the data effectively.\n\nFor further assistance, please contact GrowthLoop support.","2025-01-09T17:56:10.076Z","2025-01-09T18:02:09.958Z","19bf5a7b-1e54-4454-8808-6d4358261fac",[],[],{"_40":376,"_128":377,"_130":378,"_132":379,"_134":-5,"_13":-5,"_120":380,"_122":136,"_25":381,"_138":-5,"_139":382,"_141":383},"Connect Lob to GrowthLoop | GrowthLoop Docs","connect-lob-to-growthloop-growthloop-docs","https://docs.growthloop.com/docs/lob","In this article, we'll walk you through connecting Lob to GrowthLoop and exporting your audiences to the destination for direct mail activation.\n\n* Make sure you have a Lob account. If not, you can create one [here](https://dashboard.lob.com/register?amp_device_id=Ugb8GzGKKxYzbj4bFT4uPl)!\n\n1. Log into **GrowthLoop** and click the **Destinations** tab on the left sidebar.\n \n2. Then click **New Destinations** on the upper right side.\n \n3. Next, search for **Lob** in the destination modal and click **Add Lob**.\n \n4. In the modal, please **select/insert** the following information:\n \n * Destination Information\n * **Destination Name:** This is how the destination will be named and referred to in to the app going forward. It is helpful to make this name “marketer friendly” so everyone on your team knows it’s purpose.\n * **Sync frequency**: This is the default frequency audiences will be synced to a destination. Marketers can always change the frequency of an export, but this sets the default.\n * Credentials\n * **Secret API Key**: This is a credential for authentication when interacting with Lob’s API. There are two types of secret keys: test and live. Test keys (prefixed with test) are used in the test environment for free trial and development purposes, while live keys (prefixed with live) are used in the production environment for actual mailing and verification. You should use the appropriate key depending on whether you're testing or using the Lob service for real. Click [here](https://dashboard.lob.com/settings/api-keys) to find yours.\n5. Go ahead and select **Create**, and you will see Lob appear in your Destination table!\n \n\n6. Navigate to your list of audiences by clicking the **Audiences** tab on the left sidebar.\n7. Choose an existing audience or create a new one. Need help creating? Click [here](https://docs.growthloop.com/docs/create-an-audience) to learn how!\n8. Once created, click the **Export** button on the upper right side.\n9. Search for **Lob** in the export modal and then click **Add Lob**.\n10. Next, configure your match fields. Lob requires you to map **Name**, **Address Street**, **Address City**, **Address State**, **Address Abbreviation**, and **Address Zip**. When you're done, please click **Next**.\n11. Then configure your export settings:\n 1. **Export Name:** Automatically populated with your audience name for easy identification in the destination.\n 2. **Campaign Type:** Choose between a one-time export or an ongoing basis. Please note: If you specify ongoing, remember that each new batch replaces the previous one. For example, if your first export had 100 records and the next one had 50, Lob will only have the latest 50 records.\n 3. **Campaign Status**: Choose between existing or new.\n 4. **Campaign ID**: If the campaign status is set to **existing**, you must provide the unique identifier associated with the campaign you want to export your audience to. This identifier, resembling \"**cmp\\_33323424f3243**\", can be found in the campaign's settings page URL.\n 5. **Campaign Name**: If the campaign status is set to **new**, the Campaign ID field will change to Campaign Name. Here, you must provide a name for your new campaign, to which you want to export your audience. Ensure that the name does not exceed 40 characters.\n 6. **Export Schedule:** Set the Frequency, Start date, End date, and specific Days of the Week.\n12. Lastly, click **Export**, and you're done!\n\n> 👍\n> \n> You have successfully exported the audience to Lob!\n\nTo view it, [login](https://dashboard.lob.com/login) to your account and navigate to the **Campaigns** tab.\n\n![](https://files.readme.io/606ac2a-Untitled_11.png)\n\n> 📘\n> \n> Experiencing any issues when connecting and/or exporting to **Lob**? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and we’ll be in touch shortly to help resolve the matter!\n\nUpdated 5 months ago\n\n* * *","2025-06-20T22:58:55.696Z","b6382e23-2087-4c4b-b51d-747855a68a9a",[],[],{"_40":385,"_128":386,"_130":387,"_132":388,"_134":-5,"_13":-5,"_120":389,"_122":136,"_25":390,"_138":-5,"_139":391,"_141":392},"Core concepts: Key terms to know | GrowthLoop Docs","core-concepts-key-terms-to-know-growthloop-docs","https://docs.growthloop.com/docs/core-concepts","# Core concepts: Key terms to know\n\nLearn about core concepts in the GrowthLoop platform\n\nSources are the data clouds where your data sits - like BigQuery or Snowflake. To add a source you can head to the organization page and add a new Source Connection.\n\n> 📘\n\nDestinations are marketing, sales, and customer service applications where you send communications to customers. GrowthLoop can hydrate your destinations with customer data in a few key ways:\n\n* **Syncs:** GrowthLoop can sync specific objects and columns to your destination as attributes. This is great for syncing data fields to personalize your communications.\n* **Audiences**: GrowthLoop can sync audiences to your destination. This is great for targeting customers in your destination, without needing to copy any data from your data cloud to their system beyond customer ids.\n* **Journeys**: GrowthLoop can sequence multiple communications with customers across several destinations with journey orchestration. This is true cross-channel marketing powered by your data cloud.\n\n> 📘\n\nDatasets represent a table or view of data in the GrowthLoop platform. Each Dataset in GrowthLoop is a direct mirror of that table or view in your data cloud. No data is copied, and there is no latency between when the data is ready in your data cloud, to when it appears in GrowthLoop.\n\n> 📘\n\nAudiences are the central component of GrowthLoop's platform. The audience hub is a centralized platform for your teams to create audiences (aka cohorts, segments) in a central location for every marketing, sales, and customer service channel. You can create audience segments within minutes, source data directly from the cloud, and deploy them on your customers' preferred channels.\n\n> 📘\n\nSyncs (also known as Reverse ETL) are direct copies of data from your data cloud into a **Destination**. This can be useful for updating Salesforce CRM contact profiles for your sales team. Or updating contact profiles in Marketo to personalize your emails. We encourage customers to use **Syncs** for marketing personalization in emails, sms, and push, but strongly discourage customers from copying all their data to destination platforms due to costs they experience in destinations over the long term. The goal of Composable is to centralize your data and orchestrate that data from a single location. The goal of **Syncs** is to use it in very specific use cases to personalize customer communications.\n\n> 📘\n\nJourneys is a visual canvas that enables customers to orchestrate full programs from a central canvas. Imagine being able to design an entire churn/winback program across Email, Push, Facebook Ads, and Google Ads from a single canvas and publish it. Journeys helps leading enterprises orchestrate their revenue stack.\n\n> 📘\n\nMarve enables you to leverage the power of Generative AI to create target audiences in the GrowthLoop platform. You can interact with Marve directly via chat to generate audience target ideas, and Marve will provide proactive suggestions to you and your team for new audience targets for specific programs.\n\n> 📘\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:20.801Z","afa4e897-8639-4eac-bcd1-e029061cecbd",[],[],{"_40":394,"_128":395,"_130":396,"_132":397,"_134":-5,"_13":-5,"_120":398,"_122":136,"_25":399,"_138":-5,"_139":400,"_141":401},"Counts & Breakdowns: Analyze audience, transaction, and event data | GrowthLoop Docs","counts-breakdowns-analyze-audience-transaction-and-event-data-growthloop-docs","https://docs.growthloop.com/docs/audience-advanced-reports","# Counts & Breakdowns: Analyze audience, transaction, and event data\n\n## Audience Advanced Reports\n\nLearn how to use Audience Advanced Reports to uncover deeper insights across your audience data.\n\nWhen analyzing your audiences, it’s helpful to understand not just who’s included but why they behave a certain way. **Audience Advanced Reports** gives you deeper visibility into your audience by surfacing dataset counts from both **primary** and **related datasets** (such as _Customers_, _Transactions_, or _Events_), and allowing you to break down customers by key attributes from those tables in your dataset group.\n\nIn this article, you’ll learn how to view dataset counts, create granular breakdowns, and switch between tables to explore your audience in more detail.\n\nTo add counts from **related tables** (like _Transactions_ or _Events_), follow these steps:\n\n1. In the right-hand panel, scroll to the **Counts** section.\n2. Click the **+** icon to add a new dataset count.\n3. In the modal, select the related table you want to measure.\n4. GrowthLoop will calculate and display the total number of related records for customers matching your audience.\n\n> 📘\n> \n> Use related dataset counts to understand relationships beyond the primary table, for example, total transactions, events, or purchases linked to your current audience. The primary table count (e.g., total customers) automatically appears in the top-right corner of your audience page.\n\nBreakdowns let you explore how your audience segments across specific fields from both primary and related tables in your dataset group.\n\n1. In the right-hand panel, go to the **Breakdowns** section and click **+**.\n2. From the modal, select a table - you can choose the **primary** table (e.g., _Customers_) or a **secondary** table (e.g., _Transactions_, _Events_).\n\n> 📘\n> \n> The first table in the list represents your primary table, followed by any related secondary tables in your dataset group.\n\n3. Pick the field you’d like to use for the breakdown. Supported field types include:\n 1. **Numeric fields** (e.g., total spend, number of purchases)\n 2. **Date fields** (e.g., signup date, last purchase date)\n 3. **String and Boolean fields** (e.g., city, loyalty status, active flag)\n4. GrowthLoop will generate a visual breakdown showing how your audience is distributed across the selected field.\n\n> 📘\n> \n> Breakdowns update dynamically as you modify your audience criteria, allowing you to see how audience segments shift in real time.\n\nWhen selecting fields for counts or breakdowns, you can easily switch between **primary** and **related** tables within your dataset group.\n\n1. In the right-hand panel, go to the **Breakdowns** section and click **+**.\n2. Use your trackpad to scroll horizontally if you don’t see all connected datasets.\n3. Choose another table (e.g., _Transactions_, _Events_).\n4. The available fields will automatically update based on your selection.\n\nThis makes it easy to analyze your audience from multiple perspectives - such as viewing both customer-level (from _Customers_) and transaction-level (from _Transactions_) insights without leaving the audience builder.\n\nThe **Audience Advanced Reports** feature gives you a complete picture of your audience by connecting insights across both primary and related tables. Use it to surface key relationships, explore attribute-level patterns, and refine your segmentation for more precise and effective targeting.\n\n> 📘\n> \n> If you experience any issues or have questions, please reach out to us at [support@growthloop.com](mailto:support@growthloop.com)\n\nUpdated 9 days ago\n\n* * *","2025-10-23T18:21:00.331Z","fbad95ce-e0da-4dd4-8581-ba774b09592c",[],[],{"_40":403,"_128":404,"_130":405,"_132":406,"_134":-5,"_13":-5,"_120":407,"_122":136,"_25":408,"_138":-5,"_139":409,"_141":410},"Create a sync for Facebook conversions | GrowthLoop Docs","create-a-sync-for-facebook-conversions-growthloop-docs","https://docs.growthloop.com/docs/facebook-meta-signal-route-for-conversions","# Create a sync for Facebook conversions\n\nLearn how to create Syncs for Facebook Conversions\n\nIn this guide, we will show you how to connect Facebook (Meta) Conversions as a destination and send conversion data to your Facebook Ads Manager. Let's get started!\n\nGrowthLoop enables syncing to the following Facebook (Meta) Conversions object:\n\n| Object | Description | Sync Modes | Field Mappings (Required) | Field Mappings (Optional) |\n| --- | --- | --- | --- | --- |\n| `Conversion` | Sync and track conversion events to Facebook Ads Manager | Insert (adds new events) | `Event Name`: The type of the user event, such as AddToCart, Purchase, Search, etc

`Event ID`: The unique identifier assigned to the event

`Event Time`: When the event occurred in ISO 8601 format

`Action Source`: Wwhere conversions took place, such as email, website, app, etc | See full list of parameters [here](https://developers.facebook.com/docs/marketing-api/conversions-api/parameters) |\n\n* Have your **Facebook Pixel** handy. Follow the instructions on how to create one [here](https://www.facebook.com/business/help/952192354843755?id=1205376682832142).\n\n1. To begin, sign into the GrowthLoop Platform and navigate to the **Destinations** tab on the left sidebar. Click **New Destination** in the top right corner.\n2. In the **Select Destination** window that pops up, type **Facebook Conversions** into the search bar to find the Facebook Conversions. Click **Add Meta / Facebook Conversions**.\n3. Clicking **Add Facebook Conversions** will require you to select/insert the following information:\n 1. **Destination Name**: This is a friendly name for the destination, used to refer to it within the app.\n 2. **Sync frequency**: The default frequency for syncing audiences to a destination.\n 3. **Select Ad Account**: The Ad Account you wish to send conversion data to.\n 4. **Facebook Pixel**: This is a tracking code that measures the success of your ads. Use the same Pixel ID for both browser and server events if you have already set it up. Otherwise, follow the instructions on how to create one [here](https://www.facebook.com/business/help/952192354843755?id=1205376682832142).\n4. Select **Create**. We will validate that we have all the proper permissions to load audience data to Facebook. If successful, you should now see the new `Facebook Conversions` Destination in your list of connected destinations!\n\n5. To route conversion signals to your Facebook Ads Manager, go to the **Syncs** tab on the left sidebar and click **Create Sync** in the top right corner.\n6. Clicking **Create Sync** will require you to select/insert the following information:\n 1. Route Name:\n 1. **Name**: A friendly name for the signal route.\n 2. **Sync frequency**: The default frequency for syncing conversion signals to a destination. The options are: **15 minutes**, **30 minutes**, **hourly**, and **daily**.\n 3. **Update Rule**: The default operation for syncing conversion signals to a destination. “Update only” changes existing data, “Insert only” inserts new data, and “Insert or update” is a hybrid action that adds new data if it's not already present or updates it if it is.\n 2. Source:\n 1. **Dataset/Table**: The table that holds your conversion data for each event. Usually, it's organized within an events table.\n 2. **Dataset Unique Field(s)**: The column that contains values that are distinct for each user in the table.\n 3. **Match Field**: The column used to match and identify users from your source table in the destination system. Currently, Facebook Conversion API supports email, phone, External ID, Click ID, Browser ID, Subscription ID, Facebook Login ID, Lead ID, Client IP Address, and Client User Agent.\n 3. Destination:\n 1. **Connection**: The destination you will sync conversion data to. Please select Facebook Conversions.\n 2. **Object Type**: The event that you want to track and send to Facebook for conversion tracking and analytics. Please select Conversions.\n 3. **Match Field**: The column used to match and identify users from the destination system in your source table. Currently, Facebook Conversion API supports email, phone, External ID, Click ID, Browser ID, Subscription ID, Facebook Login ID, Lead ID, Client IP Address, and Client User Agent.\n7. Once you finish selecting/inserting the required fields, click **Save Sync**.\n8. Now it’s time to add the field mappings to enable your signal route. The Facebook Conversions API require the following information about each conversion signal be mapped:\n 1. **Event Name:** A distinct identifier for a specific customer action, which can be either a standard event like “Subscribe” or custom event. View the full list of standard events [here](https://developers.facebook.com/docs/meta-pixel/implementation/conversion-tracking#standard-events).\n 2. **Event ID:** A unique string chosen by the advertiser, required for event deduplication, matching with browser/app events.\n 3. **Event Time:** Indicates when the event occurred. Facebook will automatically convert ISO 8601 timestamps to Unix.\n 4. **Action Source:** Indicates where conversions took place. The values you can send in the field are as follows: email, website, app, phone\\_call, chat, physical\\_store, system\\_generated, and other.\n9. To map the fields, select the column that represents the **Event Name** from the drop-down under **Source**.\n10. Under the **Destination** section, select **Event Name** from the drop-down.\n11. Click **Add Mapping** to include a new Source -> Destination row underneath.\n12. Repeat steps 9 through 11 to map the remaining 3 required destination fields: **Event ID**, **Event Time**, and **Action Source**.\n\n> 👍\n> \n> You have successfully created a signal sync using the Facebook Conversions API to your Facebook Ads Manager!\n\nTo confirm that your conversion data has been received, log in to your Ads account and navigate to the **Event Manager** page.\n\n![](https://files.readme.io/a7bfe8f-image.png)\n\n> 📘\n> \n> If you experience any issues when connecting to or creating syncs to Facebook (Meta) Conversions, please reach out to us at [support@growthloop.com](mailto:support@growthloop.com), and we’ll be in touch shortly to help resolve the matter!\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:35.468Z","1deababb-d796-42ef-89a1-fb723d4e8c2e",[],[],{"_40":412,"_128":413,"_130":414,"_132":415,"_134":-5,"_13":-5,"_120":416,"_122":136,"_25":417,"_138":-5,"_139":418,"_141":419},"Create a sync for Google Ads conversions | GrowthLoop Docs","create-a-sync-for-google-ads-conversions-growthloop-docs","https://docs.growthloop.com/docs/google-ads-sync","# Create a sync for Google Ads conversions\n\nLearn how to create Syncs for Google Ads Conversions\n\nIn this guide, we'll walk you through syncing conversion events to `Google Ads` for a more comprehensive view of your campaign performance. Let's get started!\n\nGrowthLoop enables syncing for the following Google Ads conversion events:\n\n| Event | Description | Sync Modes | Field Mappings (Required) | Field Mappings (Optional) |\n| --- | --- | --- | --- | --- |\n| `Click Conversions` | Sync and track online actions taken after ad clicks for accurate campaign performance | Insert (adds new events) | `Conversion Action`: The specific conversion goal you previously configured in your Google Ads account

`Conversion DateTime`: When the conversion event occured in \"yyyy-mm-dd HH:mm:ss+\\|-HH:mm\" format

`GCLID`, `GBRAID`, or `WBRAID`: Unique identifier linking the conversion to the original ad click (only set one of these fields)

* _Note_\\*: You can send enhancements as click conversions by mapping the User Hashed Email(s) and User Hashed Phone(s) fields instead of using `GCLID`, `GBRAID`, or `WBRAID` | See full list of parameters [here](https://developers.google.com/google-ads/api/docs/conversions/upload-clicks#set_optional_fields_of_each_conversion_operation) |\n| `Offline Click Conversions` | Sync and track offline actions linked to ad clicks for complete attribution | Insert (adds new events) | Same fields as `Click Conversions` | See full list of parameters [here](https://developers.google.com/google-ads/api/docs/conversions/upload-clicks#set_optional_fields_of_each_conversion_operation) |\n\n1. Click **Syncs** on the left sidebar.\n2. Then click **Create Sync** on the upper right hand-side.\n3. Next, configure your sync by filling out the following fields:\n 1. Route Name\n 1. **Name**: A friendly name for the sync.\n 2. **Sync Frequency**: The default frequency for syncing data to a destination, such as \"Daily\" or \"Hourly\".\n 3. **Update Rule:** The default operation for syncing conversion signals to a destination. Only the \"Insert only\" option is supported.\n 2. Source\n 1. **Dataset/Table**: The table that holds your conversion data for each event. Usually, it's organized within an events table.\n 2. **Dataset Unique Field(s)**: The column that contains values that are distinct for each event in the table.\n 3. **Match Field**: The column used to match and identify users from your source table in the destination system. `GCLID` is recommended.\n 3. Destination\n 1. **Connection**: The destination you will sync conversion data to. Please select `Google Adwords`.\n 2. **Object Type**: The event that you want to track and send to Google Ads for conversion tracking and analytics. Please select `Conversions`.\n 3. **Match Field**: The field based on which to match source records with destination records. `GCLID` is recommended.\n4. Once you finish selecting/inserting the required fields, click **Save Route**.\n5. Now it’s time to add the field mappings to enable your signal route. Google Ads Conversion require the following information about each conversion signal be mapped:\n 1. **Conversion Action:** The action that quantifies this conversion event.\n 2. ‍**Conversion DateTime:** The timestamp when this conversion was registered.\n6. To map the fields, select the column that represents the **Conversion Action** from the drop-down under **Source**.\n7. Under the **Destination** section, select **Conversion Action** from the drop-down.\n8. Repeat steps 5 & 6 to map the **Conversion DateTime** so you have the minimum required mappings (you can always do more than the minimum required of course), until the **Update Route** button is activated.\n9. When you are ready to **update your signal route** with the newly mapped fields, you’ll be prompted with the following 2 options: `Updates only` or `Back-fill`. We recommend you go with the **Updates Only** option, especially if you’re setting up the signal for the first time.\n\n> 📘\n> \n> The **Back-fill** option is when you are updating an existing Signal Route with newly mapped fields and you’d like all your **already synced events** to have those fields backfilled for them. This operation can be very expensive and time consuming on your underlying Data Warehouse, so please choose that option if you’re absolutely sure.\n\n> 👍\n> \n> You have successfully created a sync to Google Adwords!\n\nTo confirm that your conversion data has been received, log in to your Ads account, select **Tools**, and then **Conversions** under the **Measurement** section.\n\n![](https://files.readme.io/afb2038-image.png)\n\n> 📘\n> \n> If you experience any issues when connecting to or creating syncs to Google Ads Conversions, please reach out to us at [support@growthloop.com](mailto:support@growthloop.com), and we’ll be in touch shortly to help resolve the matter!\n\nUpdated 4 months ago\n\n* * *","2024-03-20T21:02:35.637Z","1f0b2a5a-6215-4e51-92e9-ae323cd47dad",[],[],{"_40":421,"_128":422,"_130":423,"_132":424,"_134":-5,"_13":-5,"_120":425,"_122":136,"_25":426,"_138":-5,"_139":427,"_141":428},"create audience","create-audience","https://docs.growthloop.com/reference/post_api-public-audiences","post https://app.pub.prod.flywheelproducts.com/api/public/audiences\n\n| time | status | user agent | |\n| --- | --- | --- | --- |\n| Make a request to see history. | | | |\n\nClick `Try It!` to start a request and see the response here! Or choose an example:","2025-06-20T22:59:05.167Z","66aa28cf-86c0-4643-802e-00fe59ce400e",[],[],{"_40":430,"_128":431,"_130":432,"_132":433,"_134":-5,"_13":-5,"_120":434,"_122":136,"_25":435,"_138":-5,"_139":436,"_141":437},"Create Audience Recipes and templates | GrowthLoop Docs","create-audience-recipes-and-templates-growthloop-docs","https://docs.growthloop.com/docs/audience-recipes-templates","# Create Audience Recipes and templates\n\nThis article outlines the steps necessary to start saving an audience as a template and building an Audience using a Template.\n\nIf you would like to save your Audiences as a **template** for use in the future, click the dropdown next to Export audience and select **Save as new template.**\n\n![](https://files.readme.io/76ff39f-Untitled_3.png)\n\nYour saved template will be available the next time you want to build an audience using a template.\n\n![](https://files.readme.io/92b307c-image.png) \n![](https://files.readme.io/c4917f0-image.png)\n\nOnce you save an audience as a template, you can also choose to **lock** the template. You can lock / unlock the template by clicking the lock icon on the top-right hand side, next to \"Save template\" button.\n\n![](https://files.readme.io/54adb53-image.png)\n\nBuilding an audience from a locked template, will have the audience inherit all the template's filters as **non-editable**. However, you can add your additional filters to the newly created audience.\n\nIn the example below, the audience inherited the \"State = Idaho\" filter from the template, but has an additional filter where customers should not be in \"Idaho Falls\" city.\n\n![](https://files.readme.io/fbb8a95-image.png)\n\nAfter you save one or more audiences as templates, go to the **Audience Hub** page. In the top-left filter menu labeled **Audience**, click the dropdown and choose **Template**. This will switch the table view so you can see all of your saved templates.\n\n![](https://files.readme.io/a02c8ad09ad2e6a4a080ba7d03a2bd5cf0ff664ca7412dca124e4a2b452ccf91-image.png)\n\n> 📘\n> \n> **Note**\n> \n> If you experience any issues with recipes and templates, please reach out to us at [support@growthloop.com](mailto:support@growthloop.com), and we’ll be in touch shortly to help resolve the matter!\n\nUpdated 9 days ago\n\n* * *","2024-03-20T21:02:33.966Z","00f2134a-e02a-4eb4-8e62-6aebeb1a4c08",[],[],{"_40":439,"_128":440,"_130":441,"_132":442,"_134":-5,"_13":-5,"_120":443,"_122":136,"_25":444,"_138":-5,"_139":445,"_141":446},"create journey","create-journey","https://docs.growthloop.com/reference/post_api-public-journeys","post https://app.pub.prod.flywheelproducts.com/api/public/journeys\n\n| time | status | user agent | |\n| --- | --- | --- | --- |\n| Make a request to see history. | | | |\n\nClick `Try It!` to start a request and see the response here! Or choose an example:","2025-06-20T22:59:06.419Z","02dd583b-7b72-45a0-8956-94d5ba66cf48",[],[],{"_40":448,"_128":449,"_130":450,"_132":451,"_134":-5,"_13":-5,"_120":452,"_122":136,"_25":453,"_138":-5,"_139":454,"_141":455},"Criteo: Commerce Growth","criteo-commerce-growth","https://docs.growthloop.com/docs/criteo-commerce-growth","Learn how to connect and send audiences to Criteo: Commerce Growth\n\nIn this article, we'll guide you through connecting Criteo: Commerce Growth to GrowthLoop and exporting your audiences to the destination.\n\nCriteo: Commerce Growth is a performance marketing solution designed to drive sales and engagement by leveraging advanced data-driven strategies to reach potential customers across various platforms.\n\n* Make sure you have a **Criteo: Commerce Growth account**. If you don't, fill out this [form](https://www.criteo.com/talk-to-an-expert/) to get in touch with a rep!\n\n1. Log into **GrowthLoop** and click the **Destinations** tab on the left sidebar.\n \n2. Then click **New Destinations** on the upper right side.\n \n3. Next, search for **Criteo: Commerce Growth** in the destination modal and click **Add Criteo: Commerce Growth**.\n \n4. After that, follow the prompts on the Criteo consent screen to log in and delegate permissions for the appropriate advertisers. **Only users in the Admin role can grant access.**\n \n5. Finally, enter the required information in the modal and click **Create**.\n \n 1. `Destination`: Enter the name you want to give the destination.\n 2. `Sync Frequency`: Select a default export frequency to the destination.\n 3. `Select Ad Account`: Select the ad account from the drop-down menu where you want to export your audiences.\n 4. `GUM Caller ID`: This field is only required if you want to export an audience of **Criteo GUM Cookie Identifiers**. Please contact your Criteo account team to obtain it.\n\n6. Navigate to your list of audiences by clicking the **Audiences** tab on the left sidebar.\n7. Choose an existing audience or create a new one. Need help creating? Click [here](https://docs.growthloop.com/docs/create-an-audience) to learn how!\n8. Once created, click the **Export** button on the upper right side.\n9. Search for **Criteo: Commerce Growth** in the export modal and then click **Add Criteo: Commerce Growth**.\n10. Map one of the following user identifiers under **Configure Match Field Settings**: `Email`, `Mobile Ad Identifier`, `LiveRamp Identity Link`, `Criteo GUM Cookie Identifier`, `Customer ID`, or `Phone Number`. After mapping, click **Next**.\n11. Configure your export settings:\n 1. **Export Name**: Automatically populated with your audience name for easy identification in the destination.\n 2. **Campaign Type**: Choose between a **One Time** export or **Ongoing** basis.\n 3. **Audience Segment Status**: Choose between **New** or **Existing**.\n 1. **New**: Selected by default, this option will create a new audience segment of the type contact list, using the audience name, and add users to the segment.\n 2. **Existing**: When selected, you're required to input the **Audience Segment ID**. This action will add users to an existing audience segment.\n 4. **Export Schedule**: Set the frequency, start date, end date, and specific days of the week.\n12. Finally, click **Export** to send the audience to Criteo: Commerce Growth!\n\n> 👍\n> \n> You have successfully exported the audience!\n\nTo view your audience, log in to **Criteo: Commerce Growth**, click **Audiences** on the left-hand sidebar, select **Audience Library**, and then click the **Segments** tab.\n\n![](https://files.readme.io/a5a9bcb5e6e433b5fe915b5b1ae6b9f45a9015f9bf8f4176b935c6e4866d04e9-image.png)\n\n> 📘\n> \n> Experiencing any issues when connecting and/or exporting to **Criteo: Commerce Growth**? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and we’ll be in touch shortly to help resolve the matter!\n\nUpdated 5 months ago\n\n* * *","2025-06-20T22:58:38.146Z","9f962b37-1fe1-42b3-8818-9a5a5a33ccb2",[],[],{"_40":457,"_128":458,"_130":459,"_132":460,"_134":-5,"_13":-5,"_120":461,"_122":136,"_25":462,"_138":-5,"_139":463,"_141":464},"Criteo: Retail Media","criteo-retail-media","https://docs.growthloop.com/docs/criteo-retail-media","Learn how to connect and send audiences to Criteo: Retail Media\n\nIn this article, we'll guide you through connecting Criteo: Retail Media to GrowthLoop and exporting your audiences to the destination.\n\nCriteo: Retail Media is an advertising solution designed to help retailers and brands promote their products directly within retail environments, both online and offline\n\n* Make sure you have a **Criteo: Retail Media account**. If you don't, fill out this [form](https://www.criteo.com/talk-to-an-expert/) to get in touch with a rep!\n\n1. Log into **GrowthLoop** and click the **Destinations** tab on the left sidebar.\n \n2. Then click **New Destinations** on the upper right side.\n \n3. Next, search for **Criteo: Retail Media** in the destination modal and click **Add Criteo: Retail Media**.\n \n4. After that, follow the prompts on the Criteo consent screen to log in and delegate permissions for the appropriate advertisers. **Only users in the Admin role can grant access.**\n \n5. Finally, enter the required information in the modal and click **Create**.\n \n 1. `Destination`: Enter the name you want to give the destination.\n 2. `Sync Frequency`: Select a default export frequency to the destination.\n 3. `Select Ad Account`: Select the ad account from the drop-down menu where you want to export your audiences.\n 4. `Retailer ID`: Enter the unique identifier associated with your Retail Media account. You can find the ID by logging into the platform and navigating to Account Settings > Retailers.\n\n6. Navigate to your list of audiences by clicking the **Audiences** tab on the left sidebar.\n7. Choose an existing audience or create a new one. Need help creating? Click [here](https://docs.growthloop.com/docs/create-an-audience) to learn how!\n8. Once created, click the **Export** button on the upper right side.\n9. Search for **Criteo: Retail Media** in the export modal and then click **Add Criteo: Retail Media**.\n10. Map one of the following user identifiers under **Configure Match Field Settings**: `Email Address`, `User Identifier`, `LiveRamp Identity Link`, or `Retail Media Customer ID`. After mapping, click **Next**.\n11. Configure your export settings:\n 1. **Export Name**: Automatically populated with your audience name for easy identification in the destination.\n 2. **Campaign Type**: Choose between a `One Time` export or `Ongoing` basis.\n 3. **Audience Segment Status**: Choose between `New` or `Existing`.\n 1. `New`: Selected by default, this option creates a new audience segment of the type contact list, using the specified audience name, and adds users to that segment.\n 2. `Existing`: When this option is selected, you must enter the Audience Segment ID to add users to an existing audience segment. To find the ID, navigate to Shared Library > Audiences and Segments > Contact List > Sharing Details. The ID can be found in the URL between contact-lists/ and /share. For example: \n [https://retailmedia.criteo.com/accounts/12345/demand/audiences/segments/contact-lists/45678/share](https://retailmedia.criteo.com/accounts/12345/demand/audiences/segments/contact-lists/45678/share) (the ID is 45678).\n 4. **Export Schedule**: Set the `Frequency`, `Start Date`, `End Date`, and specific `Days of the Week`.\n12. Finally, click **Export** to send the audience to Criteo: Retail Media!\n\n> 👍\n> \n> You have successfully exported the audience!\n\nTo view your audience, log in to Criteo: Retail Media. Then, click (1) **Demand** on the top navigation bar, open the (2) **Shared Library** drop-down, and select**Audiences and Segments**. Next, click (3) **Contact List** under Segments in the left-hand navigation bar.\n\n![](https://files.readme.io/b54833c600ddc1460dee7a5e8c69d7e998ff30451fde4f6ce29699c10d0823b8-image.png)\n\n> 📘\n> \n> Experiencing any issues when connecting and/or exporting to **Criteo: Retail Media**? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and we’ll be in touch shortly to help resolve the matter!\n\nUpdated 5 months ago\n\n* * *","2025-06-20T22:58:39.857Z","65e4dacc-5be0-4f79-851d-6e441ed8a4f0",[],[],{"_40":466,"_128":467,"_130":468,"_132":469,"_134":-5,"_13":-5,"_120":470,"_122":136,"_25":471,"_138":-5,"_139":472,"_141":473},"CRM Activation | GrowthLoop Docs","crm-activation-growthloop-docs","https://docs.growthloop.com/docs/crm-activation-suite","Here at GrowthLoop, we often say that our product is “built for marketers”. But did you know that GrowthLoop also has tremendous capabilities to perform list orchestration and data activation to CRM platforms as well? These CRM platforms, most often leveraged by sales teams, act as a downstream, pseudo-data warehouse where all of the information around Contacts, Accounts, Leads, etc. is stored to provide your sales team the latest & greatest information to aid in closing sales and driving revenue for your organization. CRM platforms, such as Salesforce and Microsoft Dynamics, are an integral part of almost all organizations today, and GrowthLoop wants to help increase the efficacy, while reducing the management headaches, of such systems.\n\nOne common issue we see with many CRM platforms today is that they are quick to become ‘out of control’ with manual data entry often leading to scores of duplicates, incorrect data transfer, and a massive time suck for your analytics and sales management teams to perform. What if, instead, we could leverage a data warehouse to source, clean, and compile data and seamlessly sync that to our favorite objects in CRM to ensure everything is up-to-date and abiding by precise business rules? What if we could also leverage a no-code Audience Builder to identify groups of high-value people and automate the creation of tasks so that our sales team always has a valuable opportunity to pursue? Well, with GrowthLoop, all of this is not only possible, but also driving incredible value for many of our clients today.\n\nIn this article, we want to highlight the three major tools we have built to empower GrowthLoop as a flexible solution for revenue & data teams, enabling data activation to (and from) CRM platforms with the data warehouse. These tools are: **CRM Syncs**, **CRM Audiences**, and **CRM Ingest**. As we dive further into each of these tools below, please keep in mind that the functionality is the same no matter which CRM platform your organization leverages today, be it Salesforce, Dynamics, HubSpot, or any others.\n\nThe first tool in GrowthLoop’s arsenal to empower CRM platforms is **Syncs** (formerly known as Signal Router)**.**\n\nSyncs are, to keep it short, GrowthLoop’s Reverse ETL solution. With Syncs, you can connect any table or view from your cloud data warehouse and sync all records with your desired object/entity of choice within CRM. This means that we can leverage the data warehouse for what it’s best at doing (modeling data) and ensure our CRM destination reflects the most accurate reality, as built in your warehouse. An organization can build out a ‘golden view’ of their contacts, accounts, leads, assets, opportunities, or any other CRM object within their data warehouse and seamlessly sync those clean, golden records to populate and update CRM for all downstream users to leverage. No longer will your sales team question if the phone number provided for a lead is the most up-to-date number to call!\n\nWhen setting up a Sync in GrowthLoop, there are just a couple, quick configuration options to select before you are on your way to syncing any/everything you want to CRM!\n\n![](https://files.readme.io/3c932d0-Untitled.png)\n\nFrom top to bottom:\n\n* **Name:** The name of this new Sync.\n* **Sync Frequency**: How often do you want to check for updates in the data warehouse and sync those updates into CRM.\n* **Update Rule:** What actions do you want to perform when syncing records into CRM, including:\n * Insert or Update: Insert any records we do not find already existing in CRM, or Update records we do find (aka ‘Upsert’). Our most commonly-used Update Rule.\n * Insert Only: Only insert records from the table that are not found in CRM, ignoring records that already exist. Great for backfilling objects.\n * Update Only: Only update records from the table that are found in CRM, ignoring records that do not exist in CRM at time of sync. Great for connecting large tables without the worry of creating ‘too much’ in CRM.\n* **Source**\n * Dataset/Table: The table or view in your data warehouse that you want to connect and use for this Sync. Please note that this dropdown will only populate with tables/views that have already been connected to GrowthLoop via the Datasets page.\n * Dataset Unique Field(s): The unique key on this table to indicate to GrowthLoop how to count how many records need to be tried in the sync. This should be pre-populated with the unique key value selected when connecting the table/view into GrowthLoop.\n * Match Field: The field on the table/view that GrowthLoop should use to lookup records in CRM to determine if a record already exists or not, and how to match on the record to send field-level updates.\n* **Destination**\n * Connection: The CRM Destination connection you want to leverage in this Sync. These connections could be to Sandbox or Production CRM environments.\n * Object Type: The CRM Object or Entity that we want to ‘point’ this Sync to. Common examples being: Contacts, Accounts, Leads, Opportunities, Campaigns, Assets, Events, Survey Responses, etc. Syncs also has the capability of pointing at both ‘out of the box’ CRM Objects and custom-built Objects.\n * Match Field: The field on the CRM Object records that GrowthLoop is ‘looking up’ to determine if a record from the connected table already exists or not as a record within the CRM Object. This field should match to the ‘Match Field’ selected just to the left under ‘Source’. If you are wanting to use exact CRM GUIDs for matching… this is doable, but does require some backend configuration to get working properly. Please reach out to your GrowthLoop representative for assistance if looking to use GUIDs (ex: Salesforce IDs) for matching or any field mapping.\n\nThen, after saving the overall Sync, comes the final step - field mappings:\n\n![](https://files.readme.io/8037f3c-Untitled_1.png)\n\nMapping the fields from your underlying table or view to the fields in CRM that we want to update is the final step in setting up any Sync. This step allows you to decide which fields from the connected table we actually want to update on the CRM records and provides the flexibility to map a ton of different kinds of fields, so long as the data types line up. You can map the most up-to-date contact information for your Contacts, important flags for your sales team to know, linkages to other CRM Objects such as Accounts or Owners, or any other custom field you want to build within your Objects to house important data for end users to have access to!\n\nSyncs were designed and built to be highly flexible depending on the use case. Each Sync can vary widely in scope, from syncing entire Contact objects with millions of records to syncing small, custom objects that help form linkages within CRM. There are no limits to the number of Syncs you can set up!\n\nFor all the reasons and capabilities listed above, we lovingly call Syncs our ‘Foundational Tool’ when it comes to CRM. With Syncs, you can ensure the ‘foundation’ of your CRM is as accurate and clean as a table in your data warehouse, democratizing data for your revenue teams and enabling greater automation to be built on top with tools such as… CRM Audiences.\n\nThe second tool in GrowthLoop’s arsenal to empower CRM platforms is, for lack of a better name, **CRM Audiences**.\n\nCRM Audiences leverage the power of GrowthLoop’s Audience Builder to segment and identify key groups of people that you want to act upon using your CRM workflows. With CRM Audiences, you can easily export the same audiences leveraged by your marketing teams for advertising outreach, or brand new audiences specifically meant for sales outreach, to your CRM platform to automate the creation of ‘action records’, like Opportunities, Activities (Emails, Phone Calls, Tasks, Appointments), or Campaigns. You can even leverage CRM Audiences to selectively create new Contact/Account/Lead records within CRM that can then be constantly updated via CRM Syncs. Both CRM tools often are used in conjunction with each other for the most powerful CRM activation outcomes.\n\nLet’s dive a bit deeper into how CRM Audiences work today:\n\n**Building your CRM Audience**\n\nThe first step to leveraging CRM Audiences is to, well, build an audience! Using GrowthLoop’s no-code audience builder is easy to quickly identify key groups of people that you want to act upon within CRM. Examples of such groups could be: High Value Leads, Existing Customers at Risk of Churn or New Sign-Ups (warranting a friendly phone call).\n\n![](https://files.readme.io/06e0cd0-Untitled_2.png)\n\n**Setting up your Export Configuration:**\n\nOnce you have your audience all set and ready to export, next comes your CRM Audience export configuration (aka what do you want to do with this group of people in CRM).\n\nWith CRM Audiences today, you have over 145K permutations of options to choose when sending an audience to CRM. While this might sound overwhelming at first, we promise the selections are straightforward and easy to configure exactly how you hope your audience to perform when hitting CRM. These selection options have been designed and built in conjunction with many of our current clients to fit their desired outcomes, and thankfully cover a very wide set of use cases. The following are screenshots showing an example CRM Audience configuration, along with descriptions explaining how this works and what other options are available today:\n\n![](https://files.readme.io/cc1f657-Untitled_3.png)\n\nWhen activating a newly-connected CRM destination for the first time, you will be given the option to ‘Activate’ your destination configuration options. After clicking ‘Activate’, you will see a new, fairly long pop-up that enables us to begin selecting our desired actions.\n\n![](https://files.readme.io/45d7930-Untitled_4.png)\n\nAt the top of this Activation Modal you will find three, global settings that help inform how the rest of the CRM Audience actions take shape. These global settings are:\n\n* Matching Selection\n * Help GrowthLoop know your primary ‘people’ object of choice, namely Accounts or Contacts. We know organizations can think differently around what/whom constitutes an Account versus a Contact, so we want to provide the flexibility of being able to look up either and perform actions upon either object. Leads will always be part of the ‘lookup journey’, but can be ignored later on in the selections should your organization not leverage the Leads object.\n * As of today, CRM Audiences only operates in the ‘standard, out-of-the-box’ CRM Objects (Accounts, Contacts, Leads, Opportunities, etc.) and cannot support custom objects. This will likely change over the coming months as we invest further into our CRM suite of tools, but please do keep this in mind for your first CRM Audiences. If your organization heavily leverages custom objects only, then Syncs can likely cover many use cases when combined with clever data modeling techniques!\n* Dynamic Opportunity Owner Assignment\n * Should the desired outcome (and selections below) be to create Opportunities on matching records, should GrowthLoop lookup that entity’s (ie: Account’s / Contact’s / Lead’s) owner and add that owner as the owner of the newly created Opportunity?\n * If yes, GrowthLoop will dynamically add owners to new Opportunities to match the ownership of the underlying person record. If no, then you will be given the option further on in the selection criteria to assign all newly-created Opportunities to a single Owner instead. The latter can be helpful when a manager wants to manually reassign opportunities themself, or if you have a round-robin queue already setup in your CRM and assigning Opportunities to this queue is all that is needed to kick-off that reassignment workflow.\n* Dynamic Activity Owner Assignment\n * Exact same logic as the Dynamic Opportunity Owner Assignment above, but now leveraged should an Activity (email, phone call, task, or appointment) be the desired action to be created on an entity instead of an Opportunity.\n\n![](https://files.readme.io/fbd7587-Untitled_5.png)\n\nAt the bottom of the Activation modal, you will find the final global setting for your CRM Audience Destination before getting into the desired actions and lookup journey - Field Mapping for Matching / Look-Ups. This will look nearly identical to Field Matching in CRM Syncs, and the purpose it to tell GrowthLoop how to search for Accounts, Contacts, and/or Leads within your CRM platform to know if they exist and how to act should we find them (or not).\n\nThe top set of Field Matching input boxes allow you to select the field from your connected Users table (on the left) that should be used to lookup a specific field within CRM (on the right) for your Primary Entity (Contacts or Accounts, depending on the global selection at the top of the Activation Modal). The bottom set for Field Matching input boxes does the same, but is for your Leads object. Usually, the lookup criteria is the same for Accounts/Contacts as it is for Leads, but we do want to provide the flexibility should field availabilities or lookup logic be different between the two.\n\n**It is now time to begin our CRM Audience ‘Look-Up Journey’!**\n\nNow that we have selected all of our global settings, it’s time to begin a mini look-up journey to determine what actions GrowthLoop should perform should we find Audience members within any existing objects in CRM at time of export. The ‘Look-Up Journey’ detailed below was designed on purpose to start with as niche of a look-up as possible and then slowly expand our search radius as we go to ensure we a) act upon the most-established matching records in CRM first and b) do not accidentally create duplicates via desired actions of less-established matching records.\n\nThe first, most niche group we will search for are **Accounts or Contacts with Existing Opportunities:**\n\n![](https://files.readme.io/f4e24fa-Untitled_6.png)\n\nLet’s say we have an audience of 100 people that we are exporting to CRM and want to perform actions depending on how these 100 people already reside within CRM today. To begin our look-up journey, we are going to first look to see if any of these 100 people exist today in CRM as a Contact (or Account) with an existing Opportunity. The reason being that should we find anyone that matches this criteria (has an Opportunity), your action selection might be different knowing that this Contact/Account already has an open opportunity against them, or has had previous opportunities that were Closed Lost.\n\nYou have multiple look-up options within this Matching Group to get even more specific of the kinds of Opportunities these Contacts/Accounts might have, such as:\n\n* Opportunity Types\n * Look for Contacts/Accounts that have Opportunities of a specific type.\n* Opportunity Owners\n * Look for Contacts/Accounts that have Opportunities with a specific Owner.\n* Opportunity Stages\n * Look for Contacts/Accounts that have Opportunities of specific stages.\n\nThen, should we find any Contacts/Accounts that have Opportunities of these specific selections and are in our Audience, what action should GrowthLoop perform? Here is a sample of the many actions that can be selected for this Matching Group:\n\n![](https://files.readme.io/1e8f62a-Untitled_7.png)\n\nLastly, depending on your selected action, you have the ability to map desired record types, stages, or owners (depending on your global settings) as GrowthLoop creates and maps these actions to the found entity:\n\n![](https://files.readme.io/61f6a20-Untitled_8.png)\n\nGreat! Let’s say of our initial list of 100 audience members, we have found 5 matching Contacts with Existing Opportunities and have created a brand new Opportunity for our team to pursue on each of the Contacts… Those 5 audience members are now crossed-off our list, and we have 95 audience members remaining to figure out what to do with.\n\nNext comes our second search, for **Accounts or Contacts without Existing Opportunities:**\n\n![](https://files.readme.io/4319341-Untitled_9.png)\n\nNow that we have found all audience members that already have an Opportunity record associated with them, let’s search if any audience members exist today in CRM as an Account or Contact but **does not** have an associated Opportunity record. And if we find them, what action do we want to perform (similar to the previous Matching Group).\n\nLet’s say that we find 30 audience members that fall into this bucket, and as a result, receive an Opportunity or Activity on their record for our Sales team to pursue. We have now found 35 audience members in total across the first two Matching Groups, and now we have 65 people remaining from our initial audience of 100 people to figure out what to do with.\n\nNow that we have found all late-stage ‘people objects’, let’s check to see if any of the remaining 65 people exist as a Lead in CRM today! Onto our third Matching Group: **Matching Leads**\n\n![](https://files.readme.io/eff16b0-Untitled_10.png)\n\nAt this point, you might be thinking… “What if we match upon Lead records that have already been converted into Accounts or Contacts? I don’t want to create actions on old records that now have a later-stage record already built.” The answer to this thought is exactly why we have designed our mini ‘look-up journey’ the way we have - to ensure we find the latest stage records first and act upon those before looking at earlier stage records such as Leads.\n\nWhen finding audience members within the Leads CRM Object, you are given options for adding Activities to the Lead or to bulk convert all Leads into later-stage records such as Accounts and/or Contacts. The decision on which selection to choose ultimately comes from how your Audience was built. Was this an Audience of super high-value customers that you want to ensure are late-stage records within CRM? Or was this merely an audience of prospects that you want your Sales team to call and hopefully convert into paying Contacts down the road? These are the questions we encourage you to ask yourself as you design your CRM Audience export configurations.\n\nTo continue on with our hypothetical audience export, let’s say that you found 40 audience members as Leads within CRM, meaning that, overall, you have now acted upon 75 out of 100 audience members, and only 25 remain. This leads us to our final Matching Group - **Non-Matching Accounts/Contacts or Leads:**\n\n![](https://files.readme.io/76ce4ef-Untitled_11.png)\n\nAt this point, we have already searched for and found all audience members that already exist as late-stage or early-stage ‘people objects’ within CRM. Any audience members remaining must not exist in CRM today (per the matching logic defined in the global settings) and thus we need to determine what action we want to perform for those leftover.\n\nThis final Matching Group has the most options available for what action to perform should any audience members fall into this final bucket. From creating new Accounts, Contacts, Leads, and/or assigning Opportunities or Activities to these newly created records - this is all possible with CRM Audiences today. You can even selectively choose to ignore this final group and ‘Do Nothing’ should there be remaining people in your audience and you do not want any new records to be created in CRM if they do not already exist.\n\nAfter making these final selection options for our look-up journey, you are now done configuring your CRM Audience destination for this audience export and all future audience exports! _Congrats_!\n\nThe final step to export your audience to this configured CRM Audience destination is to fill out the Export Modal with just a few, remaining inputs before your audience is now exporting and automating the creation of actions for all existing and new audience members over time.\n\n![](https://files.readme.io/d017120-Untitled_12.png)\n\nThe input boxes you see on this Export Modal will vary depending on actions you have selected to perform in the Activation Modal, but here is an example of all boxes that you could come across today:\n\n* Campaign Mapping & Naming Options\n * Would you like to map all matching, audience member records to a single campaign within CRM? If yes, do you want to create a brand new Campaign to house all records or map all records to an existing Campaign?\n * If the former, you will be presented with a free-text input box to enter the desired name of your new Campaign. If the latter, you will be presented a dropdown selection box allowing you to choose the existing Campaign from your CRM that you want to associate all audience members with.\n* Opportunity Naming Option\n * If you are creating new Opportunities as part of your action selections from the Activation Modal, what do you want the title of these new Opportunities to be?\n* Lead Source Naming Options\n * If you are creating new Opportunities, what do you want the Lead Source to be populated with?\n * If you are creating new Leads, what do you want the Lead Source to be populated with?\n* Activity Selection, Naming, and Assignment Options\n * If you are creating new Activities as part of your action selections from the Activation Modal, what kind of Activity do you want to create? Options today being: Email, Phone Call, Appointment, or Task\n * What do you want the title of the new Activity to be?\n * What comments do you want written into all newly-created Activity records?\n * When do you want all Activity records to be due by?\n\nOnce you have finished entering these final inputs, you are all set and ready to export! Future audiences going to the same, already-configured CRM Audience destination will NOT have to go through the entire Activation Modal selection again, and will instead just see the input boxes from the Export Modal for each subsequent audience you are looking to export, making this whole process much, much faster for all future audience exports.\n\nNow that we have Syncs established, keeping the CRM ‘foundation’ in sync with the data warehouse, and CRM Audiences exporting to perform actions upon your CRM records, the final piece to the CRM Activation puzzle is how to ensure all downstream actions and changes within CRM are accounted for back in the data warehouse… This is where the third and final tool in GrowthLoop’s CRM Activation suite comes in - **CRM Ingest**.\n\nGrowthLoop’s **CRM Ingest** tool is pretty much exactly what the name implies - A tool for ingesting CRM data back into the data warehouse to obtain full, end-to-end visibility and data continuity with your CRM environment.\n\nHere at GrowthLoop, we are huge proponents of centralizing all of your data sources and modeling within a cloud data warehouse. This gives your team full control over how your data is modeled, updated, and ultimately used downstream for insights and activation. While GrowthLoop sits firmly on the ‘activation’ side of the equation, we know just how important it is to ensure changes made in your CRM environment are reflected across your not only reporting tools but also other downstream channels as well. This is why GrowthLoop has invested into building our own CRM Ingest tool that we are happy to help setup for your team to get all of your favorite / most important Objects from CRM piping back into your data warehouse. Not only does this greatly enhance data accuracy, but it also enables incredibly powerful data activation ‘loops’ to/from CRM using tools like Syncs and CRM Audiences!\n\nGrowthLoop is not just a ‘tool for marketers’, but a full-service data activation platform that will enable all of your revenue teams to drive greater value for your organization while gaining tremendous efficiency and automations with tools such as **CRM Syncs**, **CRM Audiences**, and **CRM Ingest**. We are here to help with all of your data activation needs, to all of your downstream channels… CRM might just be one of the more important channels to start with ;)\n\n**Interested in learning more about HOW GrowthLoop connects with your CRM environment?**\n\nCheck out the following links for the technical, integration details by CRM system:\n\n[How-To: Salesforce CRM Destination Connection](https://docs.growthloop.com/docs/salesforce-crm)\n\n[How-To: Microsoft Dynamics CRM Destination Connection](https://docs.growthloop.com/docs/microsoft-dynamics)\n\n[How-To: HubSpot CRM Destination Connection](https://docs.growthloop.com/docs/hubspot-destination)\n\n**Want to discuss further how GrowthLoop can help with your CRM Activation needs?**\n\nReach out to [support@growthloop.com](mailto:support@growthloop.com) and we will be in-touch soon!\n\nUpdated 5 months ago\n\n* * *","2025-06-20T22:58:51.881Z","1b553544-8bae-4039-829a-ae5ed0616110",[],[],{"_40":475,"_128":476,"_130":477,"_132":478,"_134":-5,"_13":-5,"_120":479,"_122":136,"_25":480,"_138":-5,"_139":481,"_141":482},"Custom attributes for audiences | GrowthLoop Docs","custom-attributes-for-audiences-growthloop-docs","https://docs.growthloop.com/docs/custom-attributes","In this article, you'll learn how to track custom attributes on your audiences for analytics and measurement.\n\nIt is often useful to add additional attributes to audiences that can be used for tracking or linking to internal concepts. A few common use cases are:\n\n* **Categorizing audiences:** You can add a `Program Name`to your audiences so you can keep track of what audiences you are using for each marketing program.\n* **Linking to campaigns:** If you are using an audience in a campaign, you can associate that `campaign id` with each audience.\n* **Leveraging existing analytics assets:** You can add a custom attribute that serves as a join key to any existing analytics tables that want to reference audience membership and personalization data.\n\nIf an audience is created from a Template, then all of its custom attributes (keys & values) are also inherited by the audience. However, you can further modify or edit those inherited custom attributes.\n\n \n\n1. On Home Page, in action card click `Create Audience`\n2. Choose your `Dataset Group`\n3. Choose how you want to create your `Audience`: `Start with Basics`, `Start from Scratch`, etc.\n4. On the Audience Canvas, in the subheader menu select `Settings`\n5. Under `Additional Custom Attributes` click `Add Custom Attribute`\n6. Add your `Label`: The label is the name of the attribute. For example: \"campaign\\_id\".\n7. Add your `Value`: The value is the input for your attribute. For example: The actual campaign id you want to associate with this audience. Note: Your label and values cannot have spaces, but can use underscores.\n\n![](https://files.readme.io/9ef0bb3-sample_audience_custom_attribute.png)\n\n1. On Home Page, in left-hand menu select `Audiences`\n2. Click on the audience that you would like to add `Custom Attributes` to.\n3. On the `Export` button click the dropdown arrow and select `Edit`\n4. On the Audience Canvas, in the subheader menu select `Settings`\n5. Under `Additional Custom Attributes` click `Add Custom Attribute`\n6. Add your `Label`: The label is the name of the attribute. For example: \"campaign\\_id\".\n7. Add your `Value`: The value is the input for your attribute. For example: The actual campaign id you want to associate with this audience. Note: Your label and values cannot have spaces, but can use underscores.\n\nEvery audience snapshot will contain your custom attributes. This is very useful so you can join to other tables you have internally and utilize in your business intelligence platform.\n\nYou can access your attributes direcatly in your data cloud:\n\n* Within your `flywheel_syste` dataset, query snapshotting delta table for the audience you added custom attributes to.\n* Each `Custom Attribute` will have its own column where:\n * `Column Name`: This will contain the Label provided for custom attribute on audience.\n * `Value`: This will contain the `Value` provided for custom attribute on audience.\n\n![](https://files.readme.io/38a9ed8-custom_attributes_in_data_cloud.png)\n\nIf you have any questions on how to utilize `custom attributes` please let us know at [support@growthloop.com](mailto:support@growthloop.com)\n\nUpdated 5 months ago\n\n* * *\n\n* [Export an Audience](https://docs.growthloop.com/docs/export-an-audience)","2025-06-20T22:58:09.002Z","ce6034d3-652a-48e7-a3ea-959d18e8dccc",[],[],{"_40":484,"_128":485,"_130":486,"_132":487,"_134":-5,"_13":-5,"_120":488,"_122":136,"_25":489,"_138":-5,"_139":490,"_141":491},"Custom attributes in Journeys | GrowthLoop Docs","custom-attributes-in-journeys-growthloop-docs","https://docs.growthloop.com/docs/custom-attributes-1","Why and how to best take advantage of custom attributes in your journeys\n\nIn this article we will walk through the power of custom attributes to better tag your customers as they flow through a journey.\n\nCustom attributes allow you to tag each customer as they pass through journey nodes. It's a great way to add context to your customers as they flow through your journey and reference them in your reports or use those as personalization fields.\n\nKeep in mind that a journey must be saved first, before its custom attributes become available as a personalization / additional field in an export node.\n\nThe following node types currently support custom attributes:\n\n* Entry node\n* Criteria node\n* Destination node\n* Experiment node (on each variation)\n\nby navigating to the node's settings tab and adding your custom attributes.\n\n**Note** Criteria nodes allow you to have different custom attributes for the success vs. failure paths as shown below:\n\n![](https://files.readme.io/8b0eed7be54935da54c09ab0798f8c1a0c2608d35eab5bb56775ab3a64e2e042-image.png)\n\nWhat's extra powerful about custom attributes is that your values can either be:\n\n* A static text value\n* A formula\n\n![](https://files.readme.io/422f7f61755593a0dc8716a895c4e29949af87a907f3750f4c2a75596e6a6f31-image.png)\n\nWhen choosing an **Attribute Formula**, you can use several SQL statements as follow:\n\n![](https://files.readme.io/226bdd7883b536d4af5f971dee56541696750f4466a505962f0fecac30c1cb2c-image.png)\n\n \n\n| Referencing your key attributes | Description | Example Values |\n| --- | --- | --- |\n| Referencing the Primary Dataset `users.x` | * \\*x\\*\\* can be any field in the primary dataset of the entry node audience

You should always reference `users` regardless of the name of the table/schema/catalog | `users.city`
`users.gender` |\n| Referencing GrowthLoop's System Fields `metadata` | These are GrowthLoop's details of the Journey. | `metadata.journey_name`(The user defined name of the journey)

`metadata.journey_id` (The UUID of the journey (matches the UUID on the journey page) |\n| Referencing the Journey Table `journey` | These are GrowthLoop's details on the node within the journey | `journey.step_id` - The current node ID (matches the UUID in the canvas)

`journey.run_id` - The current run ID (matches the UUID in the Step Activity tracker)

`journey.created_at` - The timestamp of when the user entered the node |\n| Referencing previously defined custom attributes `glca\\_` | Allows any node in the journey to reference previously defined custom attributes, where **glca** stands for GrowthLoop Custom Attribute | If you define a custom attribute called `my_custom_attribute` in a preceding node, then you can access it with `journey.glca_my_custom_attribute`

**Nullifying Custom Attributes**
Custom attributes can be nullified by setting the key of the attribute, but leaving the value as empty |\n| Referencing a value from a secondary table in your DatasetGroup `secondary table's name` | Allows you to define a custom attribute from a secondary table. | In order to reference your secondary table in the custom attribute formula, you can simply call the table and it's corresponding field -- for example: `transactions.transaction_value` |\n\n1. Building a custom attribute for each user's full address:\n \n ![](https://files.readme.io/d58b42c0ef7a48d24d58d348f5f0dd721f333fa7af5b4d92a8f7609cae056e38-image.png)\n \n2. Assign different promotion codes based on what type of users they are\n \n ![](https://files.readme.io/cdb4d60f7f3116622521578a14963edb7240a302db086f69377e8d1fd47348ed-image.png)\n \n\n \n\n3. To continue on example 2 above, we will now build a custom attribute (**promo\\_campaign**) where we combine the user's gender with the above discount code. This is so we can send them a more gender-specific promotional email campaign with the right discount code combined.\n \n ![](https://files.readme.io/7f2a8ebbc5237c812d7d42a8b9376ce89888f6137951346b33b3e1627fc6ae0e-image.png)\n \n4. Now let's create a custom attribute using a field from a secondary table in your DatasetGroup (the Transaction table). The transaction table has the **transaction\\_value** as a column which we'd like to save as the custom attribute.\n \n ![](https://files.readme.io/8f732bb326c687f8d9fa7fb4f4490aa186036b60c6ff0030137ae8edb60e7b76-image.png)\n \n \n \n\nUpdated 5 months ago\n\n* * *","2025-06-20T22:58:19.506Z","d03ea694-8bb0-45a3-8640-f34c962d66ee",[],[],{"_40":493,"_128":494,"_130":495,"_132":496,"_134":-5,"_13":-5,"_120":497,"_122":136,"_25":498,"_138":-5,"_139":499,"_141":500},"Customer journeys: An overview | GrowthLoop Docs","customer-journeys-an-overview-growthloop-docs","https://docs.growthloop.com/docs/journeys-overview","Learn how to orchestrate journeys across your entire Marketing stack\n\nWe have created the first composable journey builder to give you the ultimate flexibility in orchestrating customer journeys across your marketing and sales tools.\n\n![](https://files.readme.io/b817044-Screenshot_2024-01-24_at_2.22.31_PM.png)\n\nYou can now design an end-to-end journey for a cohort of users for key programs all from a single canvas.\n\n**Some common use cases include:**\n\n* Cross Sell programs\n* [Churn winback programs](https://www.growthloop.com/post/winback-campaign-examples-and-strategies)\n* Onboarding programs\n* Upsell programs\n* Account based marketing from paid media -> Email -> CRM Lead Routing\n\n![](https://files.readme.io/28bd3ef-Cross_Sell_-_V4_1.png)\n\nFor more information or to provide feedback to the team, please reach out to [support@growthloop.com](mailto:support@growthloop.com). We can’t wait to hear from you!\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:34.567Z","1f90135e-4e9c-4a14-bb35-04c7de1ab546",[],[],{"_40":502,"_128":503,"_130":504,"_132":505,"_134":-5,"_13":-5,"_120":506,"_122":136,"_25":507,"_138":-5,"_139":508,"_141":509},"Custom Nodes","custom-nodes","https://docs.growthloop.com/docs/custom-nodes","Custom Nodes\nLearn how to leverage custom nodes in journeys\nIn this article, we will walk you through how you can leverage custom nodes in your journeys. Custom nodes allow you to orchestrate marketing journeys with your internal data processes. Let's imagine a few key scenarios where this proves valuable:\nPrediction APIs - Your data science team has created a model to predict the likelihood for a customer to buy products in a specific category. You would like to get that prediction while the customer travels through your journey so you can make the best next decision for them.\nExperiments - Your analytics team has created a custom pipeline to assign treatment/control groups to mitigate randomization bias. Prior to exporting users in your journey to specific destinations, you would like to assign them to a treatment or control group and only export the treatment users. \nOffer Assignment - Your data engineering teams have created an internal process for assigning offers and coupon codes to each customer in a journey. You would like to get the offer assignment and specific coupon code so it can be included in your channel communications. \nWith custom nodes, you can leverage these internal processes within GrowthLoop journeys.\nLet's start with an overview of how Custom Nodes operate. They follow a few simple key steps:\nPublish Journey: Create a journey and place your custom node on canvas. Publish Journey.\nInternal Process: When users reach a Custom node in your journey it will trigger your Internal Process\nEnrichment Table: Your Internal Process is expected to write additional data about each user back to an Enrichment Table for that specific journey step.\nActivation: You can now use any data in the Enrichment Table for journey splits and destination activation. \nCriteria: Enrichment Table fields can be leveraged to further split your Journey paths.\nPersonalization:When sending users to a destination in your journey can you insert the enrichment fields as personalization.\nDefine Custom Node Type \nAirflow\nCloud Composer\nCreate Service Account with proper permissions in Google Cloud \nPermissions required:\nProvide Airflow DAG url\nProvide enrichment column names\nGrowthLoop with create enrichment table \ndataset: flywheel_system\ntablename: \\ [journey_id][step_id]\\_enrichment\nGrowthLoop will trigger DAG Url via webhook with the following parameters: \ntable_name: [journey_id][step_id]_enrichment\nstep_id: step_id\nCreate Airflow DAG to read users from journey step table, and writes to enrichment table \nDAG reads unique_ids from journey step \ndataset: flywheel_system\ntablename: \\ [journey_id][step_id]\\_enrichment\nDAG writes to enrichment table \ntable_name: [journey_id][step_id]_enrichment\nFields from enrichment tables can be used in destination nodes for use downstream in marketing channels like email and direct mail.\nFor more information or to provide feedback to the team, please reach out to solutions@growthloop.com. We can’t wait to hear from you!\nUpdated about 2 months ago","2024-03-20T21:02:34.852Z","4adf16c5-c85c-4c6e-bad2-cf994c2c8ae2",[],[],{"_40":511,"_128":512,"_130":513,"_132":514,"_134":-5,"_13":-5,"_120":515,"_122":136,"_25":516,"_138":-5,"_139":517,"_141":518},"Datasets and Models: An overview | GrowthLoop Docs","datasets-and-models-an-overview-growthloop-docs","https://docs.growthloop.com/docs/datasets-overview","# Datasets and Models: An overview\n\nLearn the core concepts of Datasets in the GrowthLoop Platform\n\nDatasets and Models allow you to configure which data you'd like to enable your teams to use from your data cloud. Our goal is to make this process as simple as possible so you can choose exactly which data you'd like to expose to your teams with as little work as possible. There are a few key concepts to understand about GrowthLoop Datasets:\n\n![](https://files.readme.io/506f48e-datasets_diagram.png)\n\n**Datasets:** Datasets represent a table or view of data in the GrowthLoop platform. Each Dataset in GrowthLoop is a direct mirror of that table or view in your data cloud. No data is copied, and there is no latency between when the data is ready in your data cloud to when it appears in GrowthLoop.\n\n**Models:** Enable analysts to create custom data models for audience building directly in GrowthLoop - without altering your underlying data architecture.\n\n**Dataset Groups:** GrowthLoop aids in creating intelligent customer segments for personalized campaigns, enhancing the customer experience. It recommends audience segments based on machine learning and the data models provided.\n\n**PII:** Personally Identifiable Information such as email, phone numbers, names, and addresses.\n\nUpdated 5 months ago\n\n* * *\n\n* [Preparing Customer Data](https://docs.growthloop.com/docs/preparing-customer-data)","2024-03-20T21:02:23.103Z","87b84175-1e89-4bc2-9890-2f2060dfb498",[],[],{"_40":520,"_128":521,"_130":522,"_132":523,"_134":-5,"_13":-5,"_120":524,"_122":136,"_25":525,"_138":-5,"_139":526,"_141":527},"DV360","dv360-2","https://docs.growthloop.com/docs/dv360-1","Export audiences from your Data Warehouse to Display & Video 360 (DV360) to plan, execute, and measure digital advertising campaigns.\nDiscover how to link Display & Video 360 (DV360) as your destination and unleash the power of exporting audiences across Google's ad channels – from Gmail and Google Display to Video and Connected TV.\nBefore connecting DV360 to the GrowthLoop application:\nYou must have a DV360 account to connect to the GrowthLoop application. If you do not, contact their sales team.\nEnsure you have an account for your GrowthLoop Audience Platform. If you don't, reach out to the admin at your company, or solutions@growthloop.com and we'll help you get sorted.\nBefore you get started, you need to contact us at solutions@growthloop.com so we can make sure GrowthLoop shows up as a partner account to link to in your DV360 account. Once that’s done, follow with the next steps.\nIn DV360, expand the Advertiser Settings menu (▼) in the left hand panel.\nClick on Linked Accounts, and then click on LINK NEW ACCOUNT.\nSelect External Data Partner from the drop down menu.\nNote: Depending on what products/features you have access to, the options may look different.\nUse the search box to search for CMU: GrowthLoop.\nClick on the link button and accept the terms to complete the product link.\nCongrats! You just linked your DV360 account to GrowthLoop 🎉\nℹ️ Note: Please get in touch with your Solutions Architect to complete this step.\nYour Solutions Architect will authenticate & connect DV360 to GrowthLoop's Ads account on your behalf. \nAfter the authentication step, you will need to share the following information with your Solutions Architect:\nDestination Name: How do you want the destination to be named and referred to in to the app going forward?‍\nDisplay & Video 360 Advertiser ID: What is the unique number for your Display & Video 360 account? To locate it, sign in to Display & Video 360 > in the navigation menu, click Advertiser Settings to expand it, then click Basic Details > find your Advertiser ID at the end of the first section.\nSync Frequency: How often do you want GrowthLoop to export audiences to DV360?\nYour Solutions Architect will click Create and you are ready to export your first audience to DV360! \nTo export an audience, navigate to an audience and click Export. \nWhen the Create Export window pops up, type Display & Video 360 into the search bar and click Select.\nBy default, the name field will auto populate to your audience name so you can easily find it in your destination. You can then select your:\ncampaign type \nexport schedule\nsync end date\npersonalization fields\nuser consent data mappings\nNote: If your customers are based in EEA (Economic European Area) or UK, we highly recommend you map the required consent fields to their corresponding columns on your Users dataset. This will ensure Google to include them as part of your targetable audiences.\nClick the Match Fields pill menu and choose your match fields\nHit Export to start exporting your audience.\nYou can then view your exported audience by logging into your DV360 Account and navigate to the Audiences section to view your audience!\nCongratulations - you have successfully exported your first audience to DV360!\nUpdated about 2 months ago","2024-03-20T21:02:38.577Z","9df1eba4-0cce-4c29-ab65-20cbd661b333",[],[],{"_40":529,"_128":530,"_130":531,"_132":532,"_134":-5,"_13":-5,"_120":533,"_122":136,"_25":534,"_138":-5,"_139":535,"_141":536},"Embed GrowthLoop audience building | GrowthLoop Docs","embed-growthloop-audience-building-growthloop-docs","https://docs.growthloop.com/docs/embed","# Embed GrowthLoop audience building | GrowthLoop Docs\n\n## Powered by GrowthLoop Embed\n\nLearn how to embed GrowthLoop audience building into your application\n\nIn this article, you will learn how to embed GrowthLoop's audience builder into an internal application or system. You can also embed our composable audience builder directly into your CRM.\n\nThis iFrame component enables you to embed GrowthLoop’s fully functional audience builder into your web application including audience inclusions, exclusions, user filters, transaction filtering, and more. You can configure what type of Audience Builder you would like to display that works for your user interface. Below is a compact version and an expanded version.\n\n> [](https://app.flywheelsoftware.com/embed?team_id=203&organization_id=190&embed_path=%2Faudiences%2Fnew&)...\n\n(see the Authentication section for full parameters)\n\n```\n/embed?organization_id=\\&team_id=\\7embed_path=%2Faudiences%2Fnew&...\n```\n\n![](https://files.readme.io/2c9e44a-embed.png)\n\nThe embed brings GrowthLoop’s destination sync into your application. Users can choose to export an audience. Users can select a destination that has been connected to the platform (50+ available). Users can then configure the frequency of how often they want their audience to sync to the destination platform.\n\n![](https://files.readme.io/432ced6-embed_exports.png)\n\nThe embed enables your end users to configure their export to the Destination for their audience.\n\n![](https://files.readme.io/54e6dc0-embed_destination_configuration.png)\n\n> 👍\n\nYou can embed our Audience List page in your interface or use our API to get a list of audiences and bring it into whatever UI you would like to use.\n\nEmbed our Audience List directly in your interface with this iFrame path:\n\n> [](https://app.flywheelsoftware.com/embed?team_id=203&organization_id=190&embed_path=%2Faudiences)...\n\n![](https://files.readme.io/1db936a-audience_list_embed.png)\n\nYou can list all audiences for a specific team and organization with metadata [via GrowthLoop’s API](https://docs.growthloop.com/reference/get_api-public-audiences).\n\nGrowthLoop writes all audiences and journey states to your Warehouse so you have full access. Here is a summary of the underlying data schemas.\n\n`snapshotting_audience_{id} _snapshot_history` Stores all the snapshots for the audience in the table\n\n`snapshotting_audience_{id} _delta_history` History of all the adds/removes for an ongoing audience sync. Along with the control/treatment assignment.\n\n`snapshotting_audience_{id} _metadata` Audit log of each run of audience snapshotting.\n\n1. Support Admins can log in to app.flywheelsoftware.com\n2. Admin can switch to Org and Team they want to set up destinations for.\n3. Admin clicks Datasets menu tab\n4. Admin can configure datasets for audience building.\n5. Admin can view all datasets set up for that org.\n\n1. Support Admins for your organization can log in to app.flywheelsoftware.com\n2. Admin can switch to Org and Team they want to set up destinations for.\n3. Admin clicks Destinations menu tab\n4. Admin can set up destinations for customers leveraging customer credentials.\n5. Admin can view all destinations set up for that organization.\n\nSupport Admins can quickly switch between different orgs and teams they are attached to.\n\nOn the Organization tab Support Admins can manage which users are associated with each team. Support Admins can also create new teams for the organization and assign users.\n\nOn the Manage tab, Support Admins can view all organizations they have set up and are a part of (your customers). \nWe are adding support for Support Admins to directly create a new Organization directly from this tab. For now, to create a new organization, get in touch with our team to setup the Org and ensure you have access ([support@growthloop.com](mailto:support@growthloop.com))\n\nThe source of the iframe will be `/embed`. The path you are requesting will be included as a parameter `embed_path`. This ensures the parameters can be verified before using the app.\n\nThe parameters are:\n\n* **organization\\_id**: (integer) id of your organization\n* **team\\_id**: (integer) id of the team to be used\n* **access\\_key**: (string) the access key from API Key generated in the GrowthLoop UI\n* **user\\_email:** (string) the email address of the user accessing the app\n* **user\\_name:** (string) the name of the user accessing the app\n* **session\\_length:** (integer) the length of inactivity before the session expires, in seconds\n* **nonce:** (string) a random non-repeated base64 value\n* **embed\\_path:** (string) the path being requested\n * `/audiences/new` create a new audience\n * `/audiences/edit` edit page for existing audience, requires passing id as a parameter\n * `/audiences/show` show page for existing audience, requires passing id as a parameter\n* **id:** (optional, integer) the id of a single record, (ex. an audience id)\n* **signature:** (string) the encoded value of the other parameters\n\nIn order to generate the `signature` you will need to use the secret key that is provided when you first generate a new API Key.\n\nThe string that is encrypted with the secret key has each string value cast to JSON, each integer value must be an integer, a new line between each value, and UTF-8 encoding enforced. No new line after the last value. The values are done in the following order:\n\n* organization\\_id\n* team\\_id\n* access\\_key\n* user\\_email\n* user\\_name\n* session\\_length\n* nonce\n* embed\\_path\n* id - only if passing value, otherwise not included\n\nThe above are then used with HMAC digest, SHA256, and base64 URL encoded to produce the signature.\n\nFor example:\n\n```\nstring = [ \n organization_id.to_i, \n team_id.to_i, \n access_key.to_json, \n user_email.to_json, \n user_name.to_json, \n session_length.to_i, \n nonce.to_json, \n embed_path.to_json,\n id.to_i # optional\n].join(\"\\n\")\n\nsignature = Base64.urlsafe_encode64(\n OpenSSL::HMAC.digest(\n OpenSSL::Digest.new('sha256'),\n api_secret_key,\n string.force_encoding('utf-8')\n ),\n padding: false\n).strip\n```\n\n```\nlet string = [\n parseInt(params.organization_id),\n parseInt(params.team_id),\n JSON.stringify(params.access_key),\n JSON.stringify(params.user_email),\n JSON.stringify(params.user_name),\n parseInt(params.session_length),\n JSON.stringify(params.nonce),\n JSON.stringify(params.embed_path),\n parseInt(params.id) // optional\n].join('\\n');\n\nlet signature = crypto.createHmac(\"sha256\", api_secret_key).update(Buffer.from(string, \"utf8\").toString()).digest(\"base64url\");\n```\n\nThe email passed in the `user_email` parameter is used to look for any existing users with that email address. If no user is found we create a new one and they are given the \"User\" role, (lowest permissions level). We also check to see if the user is part of the team (`team_id`) that is past. If they are not then they will be added to that team.\n\nPlease note that SSO is not used as part of authenticating users via embed. Users created through embed will not have the ability to login to the full application.\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:32.985Z","938e6607-1b16-4068-a9e9-2c5cd86e2e8f",[],[],{"_40":538,"_128":539,"_130":540,"_132":541,"_134":-5,"_13":-5,"_120":542,"_122":136,"_25":543,"_138":-5,"_139":544,"_141":545},"Enhanced Match Rate for paid media | GrowthLoop Docs","enhanced-match-rate-for-paid-media-growthloop-docs","https://docs.growthloop.com/docs/enhanced-match-rate","# Enhanced Match Rate for paid media\n\nLearn how to maximize your match rates for paid media destinations\n\nIn this article, you'll learn how you can maximize match rates with paid media destinations including Google Ads, Youtube Ads, Facebook Ads, TikTok Ads, TradeDesk and many more.\n\nAs paid marketers, we constantly worry about match rates for your audiences. You've spent a lot of time preparing your campaign and target list of users, only to load that audience into the paid media platform and see a **Low Match Rate**. This leaves you unable to target a majority of your target audience, and often times with unspent media budget.\n\nGrowthLoop has developed Enhanced Match Rate to increase your paid media match rates. Now, any marketer on your team can define a target audience based on your internal customer data, and sync it to a paid media destination and achieve a higher match rate.\n\n![](https://files.readme.io/237df59-2024-01-26_16.06.07.gif)\n\nToday, your match rates in paid media platforms rely on your coverage of key data points for customers like: `Name`, `Phone`, `Email`, `Address`, `Device ID`. You may only have 20% coverage for phone numbers and 60% for emails. This means the users without that data are highly unlikely to be targetable in your paid media destinations. Enhanced Match Rate automatically matches your customers to partner `Identity Spines` to add additional details about your customer such as Phone Number, Zip code, Device ID and uses those additional identifies when matching to paid media destinations. The end result. You get a higher match rate for every paid media audience you export in the GrowthLoop Platform.\n\n![](https://files.readme.io/b31cfcc-Screenshot_2024-01-26_at_4.02.51_PM.png)\n\n**Here is the process to leverage Enhanced Match Rate:**\n\n* **Build Audience:** Build an audience in GrowthLoop's Composable Audience Platform on your data cloud.\n* **Select Paid Media Destination**: Select your paid media destination (Facebook Ads, Google Ads, DV360, etc).\n* **Enhanced Match Rate:** If you have Enhanced Match Rate enabled on your Organization, GrowthLoop will automatically match your audience with a 3rd party identity spine to add additional match keys for each user in your audience.\n\n![](https://files.readme.io/e049ac9-image.png)\n\n* **Activation:** GrowthLoop will pass the enriched audience directly to the paid media destination API to achieve higher match rates for your paid media audience.\n\nFor more information on enabling **Enhanced Match Rate** in your Organization, please reach out to [support@growthloop.com.](mailto:support@growthloop.com.)\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:24.620Z","239e786f-7061-49b9-a311-b01d7544cda9",[],[],{"_40":547,"_128":548,"_130":549,"_132":550,"_134":-5,"_13":-5,"_120":551,"_122":136,"_25":552,"_138":-5,"_139":553,"_141":554},"Export audience data to Rokt | GrowthLoop Docs","export-audience-data-to-rokt-growthloop-docs","https://docs.growthloop.com/docs/rokt","# Export audience data to Rokt\n\nRokt is an e-commerce technology and marketing company that uses AI to deliver personalized offers during checkout, increasing conversions and customer retention. This article outlines the steps necessary to set up Rokt as a GrowthLoop destination and begin exporting audiences for activation.\n\nGrowthLoop uses the Rokt [Custom Audience Import API](https://docs.rokt.com/developers/api-reference/custom-audience-import) endpoint.\n\n* API Key\n* App ID\n* App Secret\n* Account ID\n\nIf you already have these credentials on hand, you can skip down to **Setting Rokt as a Destination.** If not, see below for instructions on finding your API Key, App ID, App Secret and Account ID.\n\nIn order to sync custom audiences to Rokt, the Rokt user must have a user **type of Editor** and have permissions to create and manage campaigns and calendars toggled on when creating the user\n\n![](https://files.readme.io/498caa4-Untitled.png)\n\nThe authorization header for Rokt’s Custom Audience Import API should be your account's unique API key. You must reach out to your Rokt account manager to obtain this value.\n\nIn order to find your Account ID go to the Rokt platform [my.rokt.com](https://my.rokt.com/) and log in. Then select the account you are using to connect to Growthloop and then look at the URL. Your Account ID is the number immediately following `my.rokt.com/accounts/` .\n\nFor example given the URL: `https://my.rokt.com/accounts/1324473528547594749/new-campaign/campaigns`, the Account ID is **1324473528547594749**.\n\nThe Rokt App ID and App Secret can be generated by first going to your profile settings which can be found in the bottom left corner of the Rokt platform after clicking on your user name.\n\n![](https://files.readme.io/dc3c002-Untitled_1.png)\n\nUnder the section **Generate Personal API Credentials** you can generate a new set of credentials by typing in an App Name such as “GrowthLoop” and clicking Generate. From there you can record the App ID and App Secret for the app.\n\n**Note**: This is the only time you will be able to view or copy the App Secret although you can always generate a new set of API credentials.\n\n![](https://files.readme.io/128dc61-Untitled_2.png)\n\nOnce you have all the required values you can then set up Rokt as a destination in GrowthLoop!\n\nIf you still need help generating these values you can also check out the [Rokt documentation](https://docs.rokt.com/developers/api-reference/reporting#generating-app-id-and-app-secret) for this part of the process.\n\nSelect **Destinations** from the left rail of your Flywheel home screen.\n\n![](https://files.readme.io/c448513-Untitled_3.png)\n\nClick **New** **Destination** on the top right.\n\n![](https://files.readme.io/92748a0-Untitled_4.png)\n\nScroll down to the **Email** section and click **Add Rokt**.\n\n![](https://files.readme.io/7c4be60-Untitled_5.png)\n\nA modal window will prompt you to fill out **Destination Info** and **Credentials**.\n\n![](https://files.readme.io/54e6eaf-Untitled_6.png)\n\n**Destination Name:** A custom name for your destination.\n\n**Sync Frequency:** The frequency at which GrowthLoop will export audiences to your destination (hourly or daily)\n\n**Account ID:** Your Rokt account number from the platform URL\n\n**API Key:** Your API Key given by your Rokt account manager\n\n**App ID:** Your App ID generated in the Rokt platform\n\n**App Secret:** Your App ID generated in the Rokt platform\n\nClick **Create** and you are now ready to export your first audience to Rokt! You can confirm that your Rokt account is connected by clicking **Destinations** on the left rail.\n\n![](https://files.readme.io/e5b8820-Untitled_7.png) ![](https://files.readme.io/27235b6-Untitled_8.png)\n\nFirst, **navigate to Audience** under Platform in the GrowthLoop app on the left hand side. This will bring you to the **Central Audience Hub** where you can view, filter, and search all your organization’s audiences.\n\n![](https://files.readme.io/001a0de-Untitled_9.png)\n\nThen either click **New Audience** or **select** the existing audience that you wish to export to Rokt. (Documentation on how to create an audience can be found [here](https://docs.growthloop.com/docs/create-an-audience))\n\nOnce you have selected or created your audience you should be able to select **Export** from the dropdown at the top right corner of the audience page.\n\n![](https://files.readme.io/b3adfe6-Untitled_10.png)\n\nAfter selecting export you can then search for and **Select** your Rokt destination.\n\n![](https://files.readme.io/3656c72-Untitled_11.png)\n\nYou can then select your campaign type, export schedule, and sync end date. As well as configure your match fields which by default will only be email. Click the **Export** button.\n\n![](https://files.readme.io/ad08568-Untitled_12.png)\n\nYou will be taken to the Exports tab in the audience page where your export should appear below. Once the export is complete it’s status will show **Exported** and we can then check in Rokt to find our audience.\n\n![](https://files.readme.io/35ad03f-Untitled_13.png)\n\nAfter logging in to your Rokt instance and selecting the account you are using with growthloop you should be able to find your audience by going to **Campaigns > Custom** Audiences in the left side menu.\n\n![](https://files.readme.io/8aedbcb-Untitled_14.png)\n\nOnce the audience is shown here it will be available for use in any of your Rokt Campaigns.\n\nIf you are experiencing any issues connecting to Rokt as a destination please reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and we’ll be in touch shortly!","2025-06-20T22:58:59.654Z","775171ec-0b17-47b8-9e66-987c24984d86",[],[],{"_40":556,"_128":557,"_130":558,"_132":559,"_134":-5,"_13":-5,"_120":560,"_122":136,"_25":561,"_138":-5,"_139":562,"_141":563},"Export audiences to Conversica | GrowthLoop Docs","export-audiences-to-conversica-growthloop-docs","https://docs.growthloop.com/docs/conversica","Export audiences from your data warehouse to Conversica for intelligent AI-based customer engagement.\n\nThis article will walk you through the steps to connect Conversica as a destination in the GrowthLoop web application. Once connected, you can send your audience segments to Conversia for intelligent AI-based customer engagement.\n\n* Before you begin this process, you must have a Conversica account. If you don’t, please click [here](https://www.conversica.com/request-a-demo/) to request a demo with a representative.\n\n1. When you sign into the GrowthLoop platform, navigate to the **Destinations** tab on the left sidebar and click **New Destination** in the top right corner.\n\n![](https://files.readme.io/2238ee0-Untitled.png)\n\n2. When the **Select Destination** window opens, type **Conversica** into the search bar and click **Add Conversica**.\n\n![](https://files.readme.io/5d23cb9-Untitled_1.png)\n\n3. Clicking **Add Conversica** will require you to select/insert the following information:\n \n ![](https://files.readme.io/72e92de-Untitled_2.png)\n 1. Destination Information:\n 1. **Destination Name:** This is how the destination will be named and referred to in to the app going forward. It is helpful to make this name “marketer friendly” so everyone on your team knows its purpose.\n 2. **Sync frequency**: This is the default frequency audiences will be synced to a destination. Marketers can always change the frequency of an export, but this sets the default.\n 2. Credentials:\n 1. **Username**: Your assigned Conversica username.\n 2. **Password**: Your assigned Conversica password.\n 3. **Client ID**: Your account’s unique ID.\n4. Go ahead and select **Create**, and we’ll validate we have all the proper permissions to load audience data. You should now see Conversica in your list of connected destinations!\n \n\n![](https://files.readme.io/28386c9-Untitled_3.png)\n\n5. To export an audience, you’ll need to build one first. Click **New Audience** and [Create your New Audience](https://docs.growthloop.com/docs/create-an-audience).\n\n![](https://files.readme.io/6b56594-Untitled_4.png)\n\n6. Once you finish building the audience, click **Export Audience**.\n\n![](https://files.readme.io/a83c9eb-Untitled_5.png)\n\n7. When the **Create Export** window pops up, type **Conversica** into the search bar and click **Select**.\n\n![](https://files.readme.io/58c2bd1-Untitled_6.png)\n\n8. Then in the **Export Settings** tab, configure the following fields:\n \n ![](https://files.readme.io/623115a-image.png)\n \n 1. **Export Name:** Automatically populated with your audience name for easy identification in the destination.\n 2. **Campaign Type:** Choose between a one-time export or ongoing basis.\n 3. **Rep Name (Required):** Assign the sales representative for these records within Conversica.\n 4. **Conversation ID (Required)**: Assign the contact list for these records within Conversica.\n 5. **Export Schedule:** Set the Frequency, Start date, End date, and specific Days of the Week.\n9. Next, set up your match fields in the **Match Fields** tab. Mapping **Email Address**, **First Name**, **Lead Source**, and **Source ID** is mandatory for the export process.\n \n\n![](https://files.readme.io/4ddfc20-Screenshot_2024-04-11_2.07.41_PM.png)\n\n10. Lastly, click **Export**, and you're done! Congrats on successfully exporting an audience to Conversica. To view it, login to [Conversica](https://login.conversica.com/login) and navigate to Lead Manager.\n \n ![](https://files.readme.io/a9cbc47-image.png)\n \n\nExperiencing any issues when connecting to **Conversica**? Contact us at [support@growthloop.com](mailto:support@growthloop.com), and we’ll be in touch shortly to help resolve the matter!\n\nUpdated 5 months ago\n\n* * *","2025-06-20T22:58:38.425Z","a3b8fc83-0dfc-4ecb-95d0-3063858520e6",[],[],{"_40":565,"_128":566,"_130":567,"_132":568,"_134":-5,"_13":-5,"_120":569,"_122":136,"_25":570,"_138":-5,"_139":571,"_141":572},"Export audiences to custom destinations | GrowthLoop Docs","export-audiences-to-custom-destinations-growthloop-docs","https://docs.growthloop.com/docs/custom-destinations-copy","# Export audiences to custom destinations\n\nLearn how to setup custom destinations\n\nMany clients have new destinations to which they want to send their audiences. Sometimes, these APIs are simply not supported yet or they are internal APIs built by their engineering teams. The good news is... GrowthLoop supports both on our Enterprise Plan.\n\nGrowthLoop supports the following integration patterns for destinations:\n\n* **Audience Destinations:** Most destinations support and prefer this method. If your destination platform supports the concept of user Lists, Cohorts, Segments, or Audiences, this is your integration pattern. GrowthLoop will create a List/Cohort/Segment/Audience in your destination, and then load users to that destination on an ongoing bais.\n\nTo setup your audience destination in the GrowthLoop platform here is what is required.\n\n![](https://files.readme.io/b8c7c30-Screenshot_2024-01-24_at_4.22.45_PM.png)\n\n* **Setup**\n \n * **Authentication:** Specify your API's authentication method: This is what users must enter when setting up your platform as a destination within GrowthLoop. Note: this custom destination will only show up for your organization as an option to add.\n * API Keys\n * OAuth\n * Other\n * **Match Keys** What fields can be used by GrowthLoop to match members from your data cloud to users in your custom destination. When users export to your destination they will be able to specify which fields from your connected data cloud they will use to match to these fields in your custom destination.\n * Email\n * Phone\n * Name\n * Address\n * Unique ID: A unique Internal ID generated for your users and stored in your data cloud\n * **Personalization Fields**: Specify if your platform can accept personalization fields to be used in messaging.\n* **Create Audience Endpoint:** Specify the endpoint GrowthLoop can use to create an audience in your platform (Some platforms call this a cohort/segment/list. They are all the same thing).\n \n * GrowthLoop will send a `Post` request to your endpoint including the following parameters:\n * `audience_name`: This will contain the audience name provided by your team member within GrowthLoop when they are exporting an audience.\n * `audience_id`: This is the GrowthLoop audience id. You can choose to store this in your system if you would like.\n * Your API should send a `Response` including if the audience was created successfully.\n * **Expected Response Status Code:** We expect `200` to indicate that the segment has been created. This will register in GrowthLoop that we have successfully created the audience in your platform.\n * **Expected Response Parameters:** GrowthLoop must receive certain parameters we will store on our end.\n * `custom_audience_id`: Your response should contain the `ID` created in your system to identify the segment/audience/cohort/list.\n* **Load Audience Endpoint**: Specify the endpoint GrowthLoop can use to load members to an audience in your platform.\n \n * GrowthLoop will send a `Post` request to your endpoint including the following parameters:\n \n * `custom_audience_id`: This is the ID you provided GrowthLoop when the audience was created in your platform. In this request we are using this ID to tell you which audience we are attempting to load user data to.\n * `payload`: This is the batches of user data with match keys we will send to your load data endpoint. The expectation is that your API will match these users to your platform profiles and add those users to the audience created in our first step.\n \n ```\n { \n \"schema\":\"EMAIL_SHA256\", \n \"data\":\n [\n \"\", \n \"\", \n \"\" \n ]\n }\n ```\n \n * **Expected Response Parameters:**\n * Note: the below response parameters are optional and are used in our Activity Tracker to help your team members know if their audience exports are successful and notify them of the failures and what went wrong.\n \n | Name |\n | --- |\n | custom\\_audience\\_id |\n | num\\_received (optional) |\n | num\\_invalid\\_entries (optional) |\n | invalid\\_entry\\_samples (optional) |\n \n\n> 📘\n> \n> GrowthLoop can customize requests and expected responses for your destination if you are using our Enterprise Plan. Our team of destination architects can connect live with your team to design a request/response protocol specific to your internal API needs.\n\n* * *\n\nTo setup a Custom API endpoint, contact [support@growthloop.com](mailto:support@growthloop.com). It takes <2 weeks to get your destination live for your Organization.\n\nA GrowthLoop Solutions Architect will reach out as soon as possible to begin planning the integration of your Custom API destination. Once complete, this destination will be available in your GrowthLoop web app for all your audience exporting needs!\n\nUpdated 2 months ago\n\n* * *","2024-03-20T21:02:38.138Z","47917ff9-7676-4d0f-bae5-bacf6ce557e7",[],[],{"_40":574,"_128":575,"_130":576,"_132":577,"_134":-5,"_13":-5,"_120":578,"_122":136,"_25":579,"_138":-5,"_139":580,"_141":581},"Export data warehouse audiences to Airship | GrowthLoop Docs","export-data-warehouse-audiences-to-airship-growthloop-docs","https://docs.growthloop.com/docs/airship","# Export data warehouse audiences to Airship\n\nExport audiences from your Data Warehouse to Airship for messaging, content personalization and audience management.\n\nIn this Help Center article, we will walk you through the steps to get **Airship** connected as a destination in the GrowthLoop web application. Once connected, you will be able to send your audience segments to **Airship** for marketing activation!\n\nBefore you begin this process, you must have an **Airship** account. Click [here](https://growth.airship.com/demo-request/) to get a demo from an Airship Representative.\n\n1. When you sign into the GrowthLoop platform, navigate to the **Destinations** tab on the left sidebar and click **New Destination** in the top right corner.\n\n![](https://files.readme.io/2995c15-Untitled.png)\n\n2. When the **Select Destination** window pops up, type **Airship** into the search bar and click **Add Airship**.\n\n![](https://files.readme.io/1684da0-Untitled_1.png)\n\n3. Clicking **Add Airship** will require you to select/insert the following information:\n \n ![](https://files.readme.io/5fb1104-Untitled_2.png)\n 1. Destination Info:\n \n 1. **Destination Name:** This is how the destination will be named and referred to in to the app going forward. It is helpful to make this name “marketer friendly” so everyone on your team knows its purpose.\n 2. **Sync frequency**: This is the default frequency audiences will be synced to a destination. Marketers can always change frequency of an export to **Airship**, but this sets the default.\n 2. Credentials:\n \n 1. **Region:** The region that you’re accessing the destination from.\n 2. **Access Token**: The token generated from your Airship dashboard.\n\n> 📘\n> \n> To sync audiences from GrowthLoop to Airship, the **Access Token** must have one of the following roles granted.\n> \n> * **Audience Modification:** Grants read and write permission to audience APIs, including channels, named users, segments, lists, etc.\n> * **All Access:** Grants full access to your Airship project, except Acoustic integrations.\n\n4. Go ahead and select **Create**, and we’ll validate you have all the proper permissions to load audience data to **Airship**. You should now see **Airship** in your list of connected destinations!\n\n![](https://files.readme.io/a3a52a1-Untitled_3.png)\n\n5. Navigate to your list of audiences by clicking the **Audiences** tab on the left sidebar.\n \n ![](https://files.readme.io/04bd000-image.png)\n \n6. Choose an existing audience or create a new one! Need help creating? Click [here](https://docs.growthloop.com/docs/create-an-audience) to learn how! For this example, I'll choose an existing audience named CA Customers.\n \n ![](https://files.readme.io/6758560-image.png)\n \n7. Then click the **Export** button on the upper right hand-side.\n \n ![](https://files.readme.io/f5b67bd-image.png)\n \n8. Search for **Airship** in the export modal and then click **Select**.\n \n\n![](https://files.readme.io/1c43c73-Untitled_6.png)\n\n9. Then in the Export Settings tab, configure the following fields:\n 1. **Export Name:** Automatically populated with your audience name for easy identification in the destination.\n 2. **Campaign Type:** Choose between a one-time export or ongoing basis.\n 3. **Export Schedule:** Set the Frequency, Start date, End date, and specific Days of the Week.\n\n![](https://files.readme.io/a4565c2-Untitled_7.png)\n\n10. Next, set up your match fields in the **Match Fields** tab. You'll need to map at least one field to export. You'll need to map at least one field to export. Please note, Airship will only accept values in **UUID** format.\n \n ![](https://files.readme.io/aed48b4-image.png)\n \n11. To find your audience, login to [Airship](https://go.airship.com/accounts/login) and navigate to **Audience** and then **Lists**. And that’s it! You’ve successfully exported an audience to the **Airship** to execute your campaigns!\n \n ![](https://files.readme.io/412fd62-image.png)\n \n\n \n\n> 📘\n> \n> Experiencing any issues when connecting to **Airship**? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and we’ll be in-touch shortly to help resolve the matter!\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:36.480Z","6cec563f-30d7-42b1-a947-e062f6b7d2c0",[],[],{"_40":583,"_128":584,"_130":585,"_132":586,"_134":-5,"_13":-5,"_120":587,"_122":136,"_25":588,"_138":-5,"_139":589,"_141":590},"Export data warehouse audiences to Eloqua | GrowthLoop Docs","export-data-warehouse-audiences-to-eloqua-growthloop-docs","https://docs.growthloop.com/docs/eloqua-audience-exports","# Export data warehouse audiences to Eloqua\n\nLearn how to connect and send audiences to Eloqua directly in GrowthLoop.\n\nIn this article, we’ll walk you through connecting **Eloqua** to GrowthLoop, selecting your activation destinations, and exporting your audience.\n\n**Eloqua** is a marketing automation platform that helps businesses create, manage, and optimize customer journeys through email, campaigns, and lead nurturing. It enables marketers to personalize communications, track engagement, and measure campaign performance across channels.\n\n> 📘\n> \n> Eloqua is currently available for Audience Exports only. Support for syncing to Custom Data Objects (CDOs) will be available soon.\n\n* Make sure you have an **Eloqua** account set up. If not, get in contact with [Oracle Sales](https://www.oracle.com/corporate/contact/).\n* User must have **Advanced Users – Marketing** permissions.\n\n1. When you sign into GrowthLoop, navigate to the **Destinations** tab on the left sidebar and click **New Destination** in the top right corner.\n2. In the window, type **Eloqua** into the search bar and click **Add Eloqua**.\n3. Next, select/insert the following information:\n 1. **Destination Details**\n 1. `Destination Name`: This is how the destination will be named and referred to in to the app going forward. It is helpful to make this name “marketer friendly” so everyone on your team knows its purpose.\n 2. `Sync frequency`: This is the default frequency audiences will be synced to a destination. Marketers can always change frequency of an export to Eloqua, but this sets the default.\n 2. **Credentials**\n 1. `Company Name (Site Name)`: This is the value before the backslash in your Eloqua login (SiteName\\\\Username)\n 2. `Username`: Use the username of an Eloqua account with API access.\n 3. `Password`: This is the password for the username provided above. Ensure it's the correct password for the Eloqua account you're connecting.\n4. Go ahead and select **Create**, and we’ll validate we have all the proper permissions to load audience data to **Eloqua**. You should now see it in your list of connected destinations!\n\n5. Navigate to your list of audiences by clicking the **Audiences** tab on the left sidebar.\n6. Choose an existing audience or create a new one.\n\n> 📘\n> \n> Need help creating audiences? Click [here](https://docs.growthloop.com/docs/create-an-audience) to learn how!\n\n7. On the audience page (whether you selected an existing audience or just created one), click the **Export** button in the upper-right corner.\n8. Search for **Eloqua** in the export modal and then click **Select**.\n9. In **Configure Match Field Settings**, select the column from your dataset that corresponds to the Email match field - this is required for Eloqua exports to ensure contacts are correctly matched. You can also optionally map 14 additional fields such as First Name, Last Name, Title, and Company to further enrich your audience data.\n10. Next step is to configure your **Export Settings**. This is where you define how, when, and where your audience data is sent.\n 1. `Export Name`: Automatically populated with your audience name for easy identification in the destination.\n 2. `Campaign Type`: Choose between **One Time** to export the audience once or **Ongoing** to continuously export new audience members as they qualify.\n 3. `Export Schedule`: Configure the **Frequency**, **Start Date**, **End Date**, and specific **Days of the Week** (only for **Ongoing** exports).\n 4. `Preview Audience`: Click to see a sample of your audience, including additional, match, and consent fields, to make sure everything looks right.\n11. Finally, click **Export** to send the audience to **Eloqua**!\n\nTo locate your audience, log in to your [Eloqua account](https://login.eloqua.com/) and navigate to **Audience** > **Tools** > **Shared Lists**. There, you’ll see your audience listed!\n\n> 📘\n> \n> Experiencing any issues when connecting to **Eloqua**? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and we’ll be in-touch shortly to help resolve the matter!\n\nUpdated 6 days ago\n\n* * *","2025-10-23T18:20:39.738Z","ea010108-963e-46e3-b7a6-598f618eb2ff",[],[],{"_40":592,"_128":593,"_130":594,"_132":595,"_134":-5,"_13":-5,"_120":596,"_122":136,"_25":597,"_138":-5,"_139":598,"_141":599},"Export data warehouse audiences to LiveRamp | GrowthLoop Docs","export-data-warehouse-audiences-to-liveramp-growthloop-docs","https://docs.growthloop.com/docs/liveramp-sftp","# Export data warehouse audiences to LiveRamp\n\n## LiveRamp SFTP\n\nLearn how to connect and send audiences to LiveRamp via SFTP only.\n\nExport audiences from your Data Warehouse to LiveRamp via SFTP to target them on mobile, open web, social, and CTV platforms.\n\nIn this Help Center article, we will walk you through the steps to get **LiveRamp SFTP** connected as a destination in the GrowthLoop web application. Once connected, you will be able to send your audience segments to LiveRamp via SFTP for marketing activation!\n\n> 📘\n> \n> This connection only handles the file upload - **you’ll choose where to activate those audiences later from within your LiveRamp account.**\n\n* Before you begin this process, you must have a **LiveRamp SFTP** account set up for you. If you haven’t yet requested an SFTP account, please contact your designated LiveRamp representative.\n\n1. When you sign into the GrowthLoop platform, navigate to the **Destinations** tab on the left sidebar and click **New Destination** in the top right corner.\n2. When the **Select Destination** window pops up, type **LiveRamp SFTP** into the search bar and click **Add LiveRamp SFTP**.\n3. Clicking **Add LiveRamp SFTP** will require you to select/insert the following information:\n 1. **Destination Name:** This is how the destination will be named and referred to in to the app going forward. It is helpful to make this name “marketer friendly” so everyone on your team knows its purpose.\n 2. **Sync frequency**: This is the default frequency audiences will be synced to a destination. Marketers can always change frequency of an export to LiveRamp, but this sets the default.\n 3. **Username:** The unique identifier assigned to an individual to authenticate and access the SFTP server.\n 4. **Password:** The password associated with the username to verify identity and gain access to the SFTP server.\n 5. **Host:** The network address or domain name of the SFTP server where the files will be transferred to or from.\n 6. **Port:** The specific communication endpoint on the SFTP server where the connection is established\n 7. **Upload Folder:** The designated directory on the SFTP server where files will be transferred or uploaded during the SFTP connection.\n4. Go ahead and select **Create**, and we’ll validate we have all the proper permissions to load audience data to LiveRamp SFTP. You should now see **LiveRamp SFTP** in your list of connected destinations!\n\n5. Navigate to your list of audiences by clicking the **Audiences** tab on the left sidebar.\n6. Choose an existing audience or create a new one.\n\n> 📘\n> \n> Need help creating audiences? Click [here](https://docs.growthloop.com/docs/create-an-audience) to learn how!\n\n7. Once created, click the **Export** button on the upper right side.\n8. Search for **LiveRamp SFTP** in the export modal and then click **Select**.\n9. In **Configure Match Field Settings**, select a column from your dataset that corresponds to each match field you want to use (e.g., map the column containing ramp id to **Ramp ID**, phone numbers to **Phone**, etc.). This ensures your audience data is matched correctly during export.\n10. Next step is to configure your **Export Settings**. This is where you'll define how and when your audience data is sent to the destination.\n 1. `Export Name`: Automatically populated with your audience name for easy identification in the destination.\n 2. `Campaign Type`: Choose between **One Time** to export the audience once or **Ongoing** to continuously export new audience members as they qualify.\n 3. `Export Schedule`: Configure the **Frequency**, **Start Date**, **End Date**, and specific **Days of the Week** (only for **Ongoing** exports).\n11. Finally, click **Export** to send the audience to LiveRamp SFTP!\n\n> 📘\n> \n> File ingestion can take anywhere from `12-72 hours` for it to be loaded into your LiveRamp audience and ready for distribution.\n\nTo locate your audience, log in to your LiveRamp account and navigate to the [Files](https://docs.liveramp.com/connect/en/the-files-page.html) page. There, you’ll see your audience listed along with key metadata such as **Date Transferred**, **Ingestion Status**, **Total Rows**, **Unique Records**, and **Columns**.\n\n![](https://files.readme.io/97dd9c48c6f0bef3f65919e34dd1b0e6c9c7b0f286e0ff6164e63ba140cc475f-image.png)\n\n> 📘\n> \n> Experiencing any issues when connecting to **LiveRamp SFTP**? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and we’ll be in-touch shortly to help resolve the matter!\n\nUpdated 3 months ago\n\n* * *","2024-03-20T21:02:27.919Z","0c7cbefb-1ab2-478e-9cbf-0ca3ed9a4dec",[],[],{"_40":592,"_128":601,"_130":602,"_132":603,"_134":-5,"_13":-5,"_120":604,"_122":136,"_25":605,"_138":-5,"_139":606,"_141":607},"export-data-warehouse-audiences-to-liveramp-growthloop-docs-2","https://docs.growthloop.com/docs/liveramp-activation","# Export data warehouse audiences to LiveRamp\n\n## LiveRamp Activation\n\nLearn how to connect and send audiences to LiveRamp destinations directly in GrowthLoop.\n\nIn this article, we’ll walk you through connecting **LiveRamp Activation** to GrowthLoop, selecting your activation destinations, and exporting your audience. Once the export is triggered, GrowthLoop handles the upload to LiveRamp via SFTP and routes the audience to the selected destinations.\n\nLiveRamp is a data onboarding and identity resolution platform that helps businesses activate and measure their customer data across advertising and marketing channels.\n\n> 📘\n> \n> **LiveRamp Activation** handles both the file upload via SFTP and the delivery of your audience to the selected destination, unlike [LiveRamp SFTP](https://docs.growthloop.com/docs/liveramp-sftp#/), which supports upload only.\n\n* Make sure you have a **LiveRamp SFTP account** set up and **Activation API credentials** available. If not, contact your LiveRamp rep to request them.\n* Inform your LiveRamp rep that you’ll be uploading to **GrowthLoop’s SFTP location**, and ask them to **map it to the correct Onboarding API audience**. This step is required to ensure your files are processed correctly.\n* Work with your LiveRamp rep to ensure your Onboarding API audience is **configured to match the structure expected by the Activation API**, with the following required columns:\n * `RAMPID`\n * `SEGMENT_NAME`\n* Confirm that your Onboarding API audience is configured to **support multi-valued fields**. This is necessary to prevent `SEGMENT_NAME` values from being overwritten when a RampID appears in multiple segments.\n\n1. When you sign into GrowthLoop, navigate to the **Destinations** tab on the left sidebar and click **New Destination** in the top right corner.\n2. When the **Select Destination** window pops up, type **LiveRamp Activation** into the search bar and click **Add LiveRamp Activation**.\n3. Clicking **Add LiveRamp Activation** will require you to select/insert the following information:\n 1. **Destination Details**\n 1. `Destination Name`: This is how the destination will be named and referred to in to the app going forward. It is helpful to make this name “marketer friendly” so everyone on your team knows its purpose.\n 2. `Sync frequency`: This is the default frequency audiences will be synced to a destination. Marketers can always change frequency of an export to LiveRamp, but this sets the default.\n 2. **API Credentials**\n 1. `Account ID (Username)`: Enter the Account ID tied to your Service Account.\n 2. `Secret Key (Password)`: Enter the Secret Key associated with your Service Account.\n 3. `Client ID`:Enter the Client ID associated with your Service Account.\n 4. `Organization ID`: Enter your ID associated with your organization.\n 3. **SFTP Credentials**\n 1. `Username`: The unique identifier assigned to an individual to authenticate and access the SFTP server.\n 2. `Password`: The password associated with the username to verify identity and gain access to the SFTP server.\n 3. `Host`: The network address or domain name of the SFTP server where the files will be transferred to or from.\n 4. `Port`: The specific communication endpoint on the SFTP server where the connection is established\n 5. `Upload Folder`: The designated directory on the SFTP server where files will be transferred or uploaded during the SFTP connection.\n4. Go ahead and select **Create**, and we’ll validate we have all the proper permissions to load audience data to **LiveRamp Activation**. You should now see it in your list of connected destinations!\n\n5. Navigate to your list of audiences by clicking the **Audiences** tab on the left sidebar.\n6. Choose an existing audience or create a new one.\n\n> 📘\n> \n> Need help creating audiences? Click [here](https://docs.growthloop.com/docs/create-an-audience) to learn how!\n\n7. On the audience page (whether you selected an existing audience or just created one), click the **Export** button in the upper-right corner.\n8. Search for **LiveRamp Activation** in the export modal and then click **Select**.\n9. In **Configure Match Field Settings**, select the column from your dataset that corresponds to the **RampID** match field. This ensures your audience data is properly matched during export.\n10. Next step is to configure your **Export Settings**. This is where you define how, when, and where your audience data is sent.\n 1. `Export Name`: Automatically populated with your audience name for easy identification in the destination.\n 2. `Campaign Type`: Choose between **One Time** to export the audience once or **Ongoing** to continuously export new audience members as they qualify.\n 3. `Activated Destinations`: Select one or more destinations that have already been connected and authorized in your LiveRamp account. These are the downstream channels where your audience data will ultimately be delivered.\n 4. `Export Schedule`: Configure the **Frequency**, **Start Date**, **End Date**, and specific **Days of the Week** (only for **Ongoing** exports).\n11. Finally, click **Export** to send the audience to **LiveRamp Activation**!\n\n> 📘\n> \n> LiveRamp typically takes 12–72 hours to ingest the audience, depending on the size of the file. Once ingestion is complete, GrowthLoop automatically triggers distribution to your selected destinations. Please note that each destination processes data on its own timeline. For example:\n> \n> * Facebook may take 1-5 days to fully process and activate the audience.\n> * DV360 can take 5-10 days.\n> \n> Timing may vary depending on the destination’s internal processing schedules and requirements.\n\nTo locate your audience, log in to your LiveRamp account and navigate to the [Files](https://docs.liveramp.com/connect/en/the-files-page.html) page. There, you’ll see your audience listed along with key metadata such as **Date Transferred**, **Ingestion Status**, **Total Rows**, **Unique Records**, and **Columns**.\n\n![](https://files.readme.io/97dd9c48c6f0bef3f65919e34dd1b0e6c9c7b0f286e0ff6164e63ba140cc475f-image.png)\n\n> 📘\n> \n> Experiencing any issues when connecting to **LiveRamp Activation**? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and we’ll be in-touch shortly to help resolve the matter!\n\nUpdated 3 months ago\n\n* * *","2025-10-23T18:20:19.534Z","8586facc-0ce0-49ec-b71a-379d9ccfd49f",[],[],{"_40":609,"_128":610,"_130":611,"_132":612,"_134":-5,"_13":-5,"_120":613,"_122":136,"_25":614,"_138":-5,"_139":615,"_141":616},"Flex Filters: How to create robust audiences | GrowthLoop Docs","flex-filters-how-to-create-robust-audiences-growthloop-docs","https://docs.growthloop.com/docs/how-to-use-flex-filters-to-supercharge-your-fan-targeting","# Flex Filters: How to create robust audiences\n\nWhat if you could identify fans that bought more than 5 tickets in the last 90 days? Thanks to Flex Filters this is now possible! Read on to learn more about it.\n\nFlex Filters gives you the flexibility to create robust fan audiences using signals across your users and transactions datasets. What normally would have required an analyst to manually identify the right tables and write a complex join query can now be done in just a few clicks in the app! Let me show you how step by step.\n\n* You've connected your data warehouse to GrowthLoop Audience Platform. \n Learn how to here: \n [Connect to BigQuery](https://docs.growthloop.com/docs/bigquery) \n [Connect to Snowflake](https://docs.growthloop.com/docs/snowflake) \n [Connect to Redshift](https://docs.growthloop.com/docs/redshift) \n [Connect to Databricks](https://docs.growthloop.com/docs/databricks)\n* You've connect your user, transaction, and events tables and views as Datasets in GrowthLoop. \n Learn how to here: \n [Set Up Datasets](https://docs.growthloop.com/docs/setup-datasets)\n\n1. From the homepage, Click **Create Audience**.\n\n![](https://files.readme.io/77a8cab1f3f214fa7cb8dfe102cbe16aaf22da587ab8a113252cb54d1514ecad-CleanShot_2025-01-15_at_14.44.292x.png)\n\n2. Select a Dataset that has already been set up.\n\n![](https://files.readme.io/975aa59a02eb1d3cab79ad25305172c030350a38092bb89ee172b7938f87a7bb-CleanShot_2025-01-15_at_14.45.282x.png)\n\n2. Select an option for how you'd like to create an audience. (For more info on how to [Create an Audience](https://docs.growthloop.com/docs/create-an-audience))\n\n![](https://files.readme.io/c38780424c2a878b93df3efaac81ee68b88c552bed5a381163118a5a6e7608d5-CleanShot_2025-01-15_at_14.49.242x.png)\n\n3. We've selected \"Start with the basics\" which will show you this template.\n\n![](https://files.readme.io/396627506b428443e8dee97140e5745adb5d752141b9b8cab2063b93c11d98aa-CleanShot_2025-01-15_at_14.50.382x.png)\n\n4. Under \"Other Data\", select an Event or Transaction dataset from the dropdown list.\n\n![](https://files.readme.io/6ba8cb57d542e02bf58d6f6fda6d63f4dbeadb748fc57052d3e22eb9e11b9dda-CleanShot_2025-01-15_at_14.54.402x.png)\n\n5. A new box is created in the canvas. This is the **Flex Filter**.\n\n![](https://files.readme.io/360f77b96e88fb32ad4e5b49520964b60ed4bb1f5f33c7d6c995723c5275d11f-CleanShot_2025-01-15_at_14.53.222x.png)\n\n6. The top section of the **Flex Filter** can be used to aggregate and filter the audience based on the number of events or transactions in the table.\n\n![](https://files.readme.io/5abfdd225dd6478c89f4013aef412050c67f2e80b38ee020b89c1a24bf875711-CleanShot_2025-01-15_at_15.00.402x.png)\n\n7. The aggregation can also be customized in this area by clicking \"Count\" and selecting a different option from the dropdown. Currently, options include \"Count\", \"Sum\", \"Average\" and \"Count Distinct\".\n\n![](https://files.readme.io/9bc401ef70dd92e44df81464ea2fb73cd0620f527892e73f5977639a62af4dfa-CleanShot_2025-01-15_at_15.03.082x.png)\n\n8. These are some examples of what those aggregations would look like.\n\n![](https://files.readme.io/45f4b799840e81f654a6536e851c4a3a27f2f09e9a7d1ce43fbfba1eb3971df8-CleanShot_2025-01-15_at_15.05.052x.png) ![](https://files.readme.io/362bbec87795cd479066885f0a8cdbe8cb779b855d665a9cf2bd5c615ae8623a-CleanShot_2025-01-15_at_15.05.492x.png) ![](https://files.readme.io/bcdb0f40e380b7c3483c3d1b5ec3ebef82c9f8a59b66927c63397ce454c7ee2b-CleanShot_2025-01-15_at_15.06.482x.png)\n\n8. Additional filters can be added to the Flex Filter box by typing at the bottom of the box.\n\n![](https://files.readme.io/079cfab5ef2ba5b050c601cd1d4f01f9cdbcd4e646ed7daf3894e8950e85f4b7-CleanShot_2025-01-15_at_14.58.322x.png)\n\n7. So in the example of more than 5 transations in the last 90 days, the Flex Filter would look like this.\n\n![](https://files.readme.io/e442d88414e9f30ff01289bef1c51b58e973fc63e0bcafb0b274aa092527bde8-CleanShot_2025-01-15_at_15.09.262x.png)\n\n8. Lastly, give your audience a name and click **Save**!\n\n![](https://files.readme.io/44fad6d0ff65f9d77854e92822a49bb87c38a93d257d8f8e0963b26443cc2e96-CleanShot_2025-01-15_at_15.11.532x.png)\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:34.364Z","b48022a7-f2e9-4385-9342-91093a3388d4",[],[],{"_40":618,"_128":619,"_130":620,"_132":621,"_134":-5,"_13":-5,"_120":622,"_122":136,"_25":623,"_138":-5,"_139":624,"_141":625},"GAM360","gam360","https://docs.growthloop.com/docs/gam360","GAM360\nThis article outlines the steps necessary to set up a GAM360 as a GrowthLoop destination and begin exporting audiences for activation.\nThis article outlines the steps necessary to set up GAM360 as a GrowthLoop destination which include:\nSetting up your Google Cloud Storage\nConfiguring your GAM360\nIf you don't have a GCS bucket, please refer to the first half of this document on how to set it up.\nHere are some prerequisites before you can set up GAM360 as a destination on GrowthLoop.\nLocate your network code. Find it in Ad Manager under Admin, then Global settings, and then Network code.\nEnsure an active First-Party Audience Segment exists in GAM360 for associating identifiers.\nSelect Publisher Managed population method if you don't want this segment to collect users through your inventory. Link\nExpect up to a 24-hour delay from segment creation to batch upload availability.\nCreate a Google Group containing all Google Accounts needing access to upload and view files. You must make sure that GrowthLoop’s service account is added as a group member to the Google Group\nSelect Destinations from the left rail of your GrowthLoop home screen. \nClick New Destination on the top right. \nSearch for \"GAM360\" and select this card\nA modal window will prompt you to fill out Destination Info and Credentials. \nDestination Name: A custom name for your destination.\nSync Frequency: The frequency at which GrowthLoop will export audiences to your destination (hourly or daily).\nBucket: The name of your Google Cloud Storage bucket.\nCredentials: Copy and paste the entire contents of your JSON key file here.\nNetwork Code: This is a unique identifier for your advertising network, which you can find in Ad Manager under Admin > Global Settings > Network Code.\nClick Create. You are now ready to begin exporting to your GAM360 destination, through a GCS bucket upload! You can confirm that your GAM360 is connected by clicking Destinations on the left rail.\nWhen exporting to GAM360, you will be prompted to specify a Match Field \nand the Audience Segment ID.\nAfter hitting Export, it can take up to 24 hours for you to see a list of your audiences in GAM360. However, you should be able to verify they've correctly landed in your GCS bucket, which we specified earlier. \nAfter exporting, the data file will be placed in a GCS folder at the following path: console.developers.google.com/storage/browser/gdfpcookieupload[Ad Manager network code].This folder contains individual CSV files for each member of the audience.\nExperiencing any issues connecting to Google Cloud Storage as a destination? Contact us at solutions@GrowthLoop.com and we’ll be in touch shortly!\nUpdated about 1 month ago","2024-03-20T21:02:26.725Z","be85fe8f-9d22-4ba6-955d-a0eb354ac2f1",[],[],{"_40":627,"_128":628,"_130":629,"_132":630,"_134":-5,"_13":-5,"_120":631,"_122":136,"_25":632,"_138":-5,"_139":633,"_141":634},"Getting started with data sources | GrowthLoop Docs","getting-started-with-data-sources-growthloop-docs","https://docs.growthloop.com/docs/overview","# Getting started with data sources\n\n## Overview\n\nLearn how to begin activating your internal data for marketing and sales.\n\nSources are where it all begins. GrowthLoop connects directly to your data cloud so your teams can begin creating `Syncs`, `Audiences`, and `Journeys`. We query your data in place, meaning no data is copied outside of your sources. This means no ETLs, no data copies are necessary to begin using GrowthLoop. You just connect to your data cloud and go.\n\nThere are a few key concepts to understand about Sources in GrowthLoop:\n\n1. **Source Connection:** A source connection is a set of credentials you provide to access your data cloud. These are the credentials GrowthLoop will use when querying your warehouse so you can track every query we make to activate your data.\n2. **Data Cloud:** Your data cloud is where you store your customer data. GrowthLoop is always adding support for additional data clouds so we can connect to your data wherever it sits: `BigQuery`, `Snowflake`, `Databricks`, `Redshift`, `SQL Server`, etc.\n\n![](https://files.readme.io/7f1c3a6-data_cloud_diagram.png)\n\n3. **Easy Button:**: What if you don't have much data in your `Data Cloud` today? GrowthLoop can help you import data directly into your data cloud from hundreds of applications such as Salesforce, Hubspot, Marketo, Braze, and others. Easy Button allows you to import data sources in minutes to begin using them for activation.\n4. **Event Collection**: Need to collect event data from your mobile application or website? GrowthLoop's event collection service is a simple tag for your website and mobile application to collect events and store them in your data cloud.\n\n![](https://files.readme.io/acd6b31-Screenshot_2024-01-24_at_11.37.50_AM.png)\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:21.026Z","a5824ceb-6521-447e-98ed-fdd93e16e813",[],[],{"_40":636,"_128":637,"_130":638,"_132":639,"_134":-5,"_13":-5,"_120":640,"_122":136,"_25":641,"_138":-5,"_139":642,"_141":643},"GrowthLoop Generated Fields","growthloop-generated-fields","https://docs.growthloop.com/docs/growthloop-generated-system-fields","What are \"GrowthLoop Generated Fields\" and how can you use them?\n\nIf you’ve ever exported audiences to marketing destinations like email platforms, you’ll know how important it is to have the right fields available. Typically, when exporting audience data, you include personalization fields such as city, gender, or device ID—data that helps you personalize messages and optimize your campaigns at the destination.\n\nAt GrowthLoop, we’ve decided to take this a step further by introducing `GrowthLoop Generated Fields`, a set of system-level fields designed to give you even more control and visibility over your exported audiences. These fields can simplify how you organize, track, and manage audience exports, enhancing your overall marketing process.\n\n`GrowthLoop Generated Fields` are additional system fields that accompany your audience exports. While you already export standard user properties to your destinations, these new fields provide added context to your export, making it easier to track where and when an audience was exported and tie it back to specific campaigns, journeys, or steps.\n\nWith `GrowthLoop Generated Fields`, you’re not just exporting audience data; you’re exporting valuable metadata that can help streamline your marketing efforts.\n\nWhen exporting an **Audience**, you’ll now have access to the following system fields:\n\n* `Audience ID`: A unique identifier for the audience segment being exported.\n* `Audience Name`: The name you’ve given to the audience.\n* `Export Date`: The exact date and time the export was generated.\n* `Destination Name`: The name of the destination to which the audience is being sent.\n\nIn addition, when exporting from a **Journey**, GrowthLoop provides even more context with additional fields:\n\n* `Journey ID`: The unique identifier of the Journey the audience is part of.\n* `Journey Name`: The name of the Journey.\n* `Journey Step ID`: The identifier for the specific step in the Journey that triggered the export.\n* `Journey Step Name`: The name of the Journey step at which the export occurs.\n\nAdding `GrowthLoop Generated Fields` to your export is simple. Follow these steps for exporting from either an Audience or a Journey.\n\n1. From the Home Page, select `Audiences` from the left-hand menu.\n2. Click on the audience you want to add `GrowthLoop Generated Fields` to.\n3. Select `Export`, then choose a destination that supports personalization fields (typically email destinations).\n4. In the `Export Settings` tab, under `Additional Fields`, click `Add Field` and select `Column Name`.\n5. Scroll down and choose a field labeled `GrowthLoop Generated`.\n6. Finally, click `Export`. Your audience, along with the selected `GrowthLoop Generated Field`, will now appear at the destination.\n\n1. From the Home Page, select `Journeys` from the left-hand menu.\n2. Click on the journey with the destination node where you'd like to add `GrowthLoop Generated Fields`.\n3. Navigate to the destination node and open it.\n4. In the `Configure` tab, under `Additional Fields`, click `Add Field` and select `Column Name`.\n5. Scroll down and choose a field labeled `GrowthLoop Generated`.\n6. Finally, click `Publish`. Your journey's audience, along with the selected `GrowthLoop Generated Field`, will now appear at the destination.\n\n> 👍\n> \n> Your export now includes `GrowthLoop Generated Fields` to help you organize and track your audience data with ease.\n\nUpdated 5 months ago\n\n* * *","2025-06-20T22:58:15.305Z","d4e933b6-c1a1-47cc-a6c8-a29aaa820cc5",[],[],{"_40":645,"_128":646,"_130":647,"_132":648,"_134":-5,"_13":-5,"_120":649,"_122":136,"_25":650,"_138":-5,"_139":651,"_141":652},"How to collect web and mobile app data in your data cloud","how-to-collect-web-and-mobile-app-data-in-your-data-cloud","https://docs.growthloop.com/docs/event-ingestion","With GrowthLoop, you can use events you collect from your website and mobile app that land in your `Data Cloud` to create audiences and journeys. Whether you are using MetaRouter, Google Analytics, Heap, Amplitude, Segment, Rudderstack, Snowplow to ingest events, as long as they are loading to your Data Cloud, they can be used in GrowthLoop.\n\nIf your company does not currently collect event data from your mobile and web application into your `Data Cloud` and you are looking for an easy to use solution, you can always use the `Event Collection Service`.\n\nIn this article, you'll see how to implement the `Event Collection Service` in your website. Once your event data is landing in your `Data Cloud` you can configure your `Event` tables as `Datasets` in GrowthLoop to begin using them in Audiences and Journeys in a matter of minutes.\n\n![](https://files.readme.io/1641eaf-Screenshot_2024-01-25_at_3.05.07_PM.png)\n\nYou can get started with **GrowthLoop Enabled Event Collection** (in partnership with MetaRouter), in a few simple steps:\n\n1. Setup an event processing server.\n2. Send events from your website and mobile applications to the event processing server.\n3. Implement any additional tracking methods on your properties.\n\nIt all starts with setting up your Event Processing Server.\n\n* The Events Processing Server is a single-tenant cluster that will process the events sent from your various mobile and web properties. This cluster can then write the events directly to your Data Cloud or other supported destinations.\n* GrowthLoop will setup your single-tenant Event Processing Server. This cluster will contain all the services you need to start sending events from your property to your integrations.\n* While GrowthLoop creates the cluster, we'll set up your Data Cloud as a destination. Please provide your solutions architect with your credentials and project ID.\n* Once you've created the cluster, it is time to add code to your site install the SDK for your website or mobile application to get started.\n\nOnce your event processing service is set up, you can start sending events to it. There are two primary methods for sending events from your properties.\n\n**Client to Server**: You can also choose to send events directly from your clients to your events server using SDKs supported on the following platforms:\n\n* Javascript (web)\n* iOS SDK\n* Android SDK\n* React Native SDK\n* HTTP\n\n**Server to Server**: You can send events for processing directly from your server using SDKs in the following languages:\n\n* Java\n* .NET\n* Node.js\n* PHP\n* Python\n* React Native\n* Ruby\n\nThe most common methodology for event collection is using the **Client to Server** approach. For example, here is how you kick off an integration with your website using the Javascript SDK.\n\n* Add the code snippet below to the global header of your site. Note: We do not recommend installation via a tag manager, but that may be done where absolutely necessary.\n* In the snippet, you'll need to replace `t.src = (\"https\\:\"===document.location.protocol?\"https\\://\":\"http\\://\")+\"tbd.com/\"+key+\".js\"` with wherever the file is hosted. For example, if the file was at [https://growthloop.com/files/growthloop\\_marketing\\_site.js](https://growthloop.com/files/growthloop_marketing_site.js) then that line should be \n `t.src = \"https://growthloop.com/files/growthloop_marketing_site.js` or `t.src = ./files/growthloop_marketing_site.js`\n\n```\n\n```\n\n* By default, your website will begin sending `Page` Events to the Event Processing Service.\n* Visit a few pages on your website to ensure events are processing and reaching your Data Cloud.\n* You can now begin tracking additional events on your website using method like `Track`, `Identify`, `Group` within the Javascript SDK.\n\nOnce your Javascript SDK is installed you will begin sending event to your event collection service which will begin routing them to your Data Cloud. You can setup the other SDKs to begin sending events from your other properties as well. Reach out to [support@growthloop.com](mailto:support@growthloop.com) if you need any assistance with SDK installation.\n\nAlready with this simple setup, you can connect your **page events** dataset to GrowthLoop to begin using it in building audiences and journeys based on what pages users visit in your properties. But, this is just the start of what is possible.\n\nOnce your SDK is installed you will automatically begin collecting **Page Events**. You can now start collecting events by adding **Track**, **Identify**, and **Group** methods to your properties.\n\n* * *\n\n**Page Events**: The Page event method helps you understand which web pages are being visited. It collects information related to the specific web page a user is viewing and includes that information as data within the Page event payload.\n\nHere is how page events are tracked end to end:\n\n1. **Send the event from your website/property**. While Page events are collected automatically for the sake of illustration here is how you would send one explicitly using the Javascript SDK using Javascript on your website:\n\n```\nanalytics.page([category], [name], [properties], [options], [callback]);\n```\n\n```\nanalytics.page (\"documentation\", \"Documentation Homepage\", {test_type: \"A\"})\n```\n\n2. **Event Processing Service processes the event**. The Javascript SDK page method will generate a Page event payload that will be sent to your **Event Processing Service**.\n\n```\n{\n \"timestamp\": \"2024-01-10T23:08:40.090Z\",\n \"integrations\": {},\n \"anonymousId\": \"f8cc0f85-cb4d-4f73-b16f-c251384fdf74\",\n \"type\": \"page\",\n \"properties\": {\n \"category\": \"documentation\"\n\t\t\"path\": \"/\",\n \"referrer\": \"\",\n \"search\": \"\",\n \"title\": \"metarouter documentation homepage\",\n \"url\": \"https://www.example.com/\",\n \"name\": \"Docs Homepage\",\n\t\t\"test_type\": \"A\"\n },\n \"context\": {\n \"page\": {\n \"path\": \"/\",\n \"referrer\": \"\",\n \"search\": \"\",\n \"title\": \"metarouter documentation homepage\",\n \"url\": \"https://www.example.com/\"\n },\n \"providers\": {},\n \"globalPrivacyControl\": false,\n \"consent\": {\n \"optOut\": {\n \"C0001\": false,\n \"C0002\": false,\n \"C0003\": false,\n \"C0004\": false,\n \"C0005\": false\n }\n },\n \"userAgent\": \"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36\",\n \"locale\": \"en-US\",\n \"library\": {\n \"name\": \"analytics.js\",\n \"version\": \"npm:next-1.51.3-mr.3\"\n }\n },\n \"messageId\": \"05b0eb33e6948947f15973724147e34d\",\n \"writeKey\": \"example_writekey\",\n \"sentAt\": \"2024-01-10T23:08:40.095Z\",\n \"_metadata\": {\n \"bundled\": [],\n \"unbundled\": [],\n \"bundledIds\": []\n }\n}\n```\n\n3. **Event Processing Service sends to Data Cloud**. The event payload is processed and stored in your Data Cloud in a table for consumption by GrowthLoop and can now be used in building audiences and journeys.\n\nPage events are sent on page visits by users in the **page** table.\n\n| Field | Type |\n| --- | --- |\n| id | STRING |\n| anonymous\\_id | STRING |\n| user\\_id | STRING |\n| received\\_at | TIMESTAMP |\n| sent\\_at | TIMESTAMP |\n| original\\_timestamp | TIMESTAMP |\n| timestamp | TIMESTAMP |\n| url | STRING |\n| title | STRING |\n| path | STRING |\n| integrations | STRING |\n| context\\_locale | STRING |\n| context\\_page\\_url | STRING |\n| context\\_library\\_version | STRING |\n| context\\_library\\_name | STRING |\n| context\\_user\\_agent | STRING |\n| context\\_page\\_title | STRING |\n| context\\_page\\_path | STRING |\n| context\\_consent\\_opt\\_out\\_c\\_0001 | BOOLEAN |\n| context\\_consent\\_opt\\_out\\_c\\_0002 | BOOLEAN |\n| context\\_consent\\_opt\\_out\\_c\\_0003 | BOOLEAN |\n| context\\_consent\\_opt\\_out\\_c\\_0004 | BOOLEAN |\n| context\\_consent\\_opt\\_out\\_c\\_0005 | BOOLEAN |\n| context\\_ip | STRING |\n| context\\_campaign\\_medium | STRING |\n| context\\_page\\_search | STRING |\n| context\\_campaign\\_name | STRING |\n| context\\_page\\_referrer | STRING |\n| context\\_campaign\\_source | STRING |\n| context\\_campaign\\_content | STRING |\n| context\\_campaign\\_term | STRING |\n| context\\_providers\\_facebook\\_tag\\_\\_fbp | STRING |\n| context\\_providers\\_facebook\\_tag\\_\\_fbc | STRING |\n| search | STRING |\n| referrer | STRING |\n| type | STRING |\n\n \n\n4. **Use Page Events in GrowthLoop Audiences & Journeys**: Setup your `page` table as a [dataset](https://docs.growthloop.com/docs/setup-datasets) in the GrowthLoop Platform to begin using it to build audiences and journeys based on which pages users visit on your properties.\n\n* * *\n\n**Track Events**: The Track event method records information about specific actions users are taking on your digital property. It includes a name describing the action (e.g. Button Clicked or Product Purchased) and a list of Properties about the action which help describe it further detail.\n\nHere is how Track events work end to end:\n\n1. **Send the Track event from your website/property:** Here is how you send a Track event using the Javascript SDK using Javascript on your website. Additional examples and docs can be found [here](https://docs.metarouter.io/docs/analyticsjs-ecommerce-spec).\n\n```\nanalytics.track(\"Product Viewed\", {\n product_id: \"837620387251\",\n name: \"Blue Dress\"\n});\n```\n\n2. **Event Processing Service processes the event**: The Javascript SDK page method will generate a Track event payload that will be sent to your **Event Processing Service**.\n3. **Event Processing Service sends to Data Cloud**: The Track event payload is processed and stored in your Data Cloud in a table for consumption by GrowthLoop and can now be used in building audiences and journeys.\n\nTrack events are sent on page visits by users in the **track** table.\n\n| Field | Type | Description |\n| --- | --- | --- |\n| event | STRING | Name of action being performed. |\n| properties | OBJECT | Dictionary of fields that describe the action. |\n\n \n\n4. **Use Track Events in GrowthLoop Audiences & Journeys**: Setup your `track` table as a [dataset](https://docs.growthloop.com/docs/setup-datasets) in the GrowthLoop Platform to begin using it to build audiences and journeys based on any user action you start tracking.\n\n* * *\n\nThe Identify event method allows you to tie events occurring on your digital properties to a specific, known user via the user providing an email, name or personally-identifiable information (PII) to you.\n\nThe best times to trigger an Identify call are typically:\n\n* When a user first registers or creates an account with you\n* When a user logs back in to their account\n* When a user updates their profile information, e.g. an address or email.\n\nHere is how Identify events work end to end:\n\n1. **Send the Identify event from your website/property:** Here is how you send a Identify event using the Javascript SDK using Javascript on your website:\n\n```\nanalytics.identify(\"sample_user_id\", {\n name: \"Jane Doe\",\n email: \"jane@example.com\",\n last_login: \"2024-01-26T22:54:45.961Z\"\n});\n```\n\n2. **Event Processing Service processes the Identify event**: The Javascript SDK page method will generate a Identify event payload that will be sent to your **Event Processing Service**. Here is a slimmed-down version example of a payload.\n\n```\n{\n \"type\": \"identify\",\n \"traits\": {\n \"name\": \"Jane Doe\",\n \"email\": \"jane@example.co\",\n \"last_login\": \"2024-01-26T22:54:45.961Z\"\n },\n \"userId\": \"sample_user_id\"\n}\n```\n\n3. **Event Processing Service sends to Data Cloud**: The Identify event payload is processed and stored in your Data Cloud in a table for consumption by GrowthLoop and can now be used in building audiences and journeys.\n\n**Identify Events:** Identify events should be used to capture information about who your users are. These events will be sent to the `identify` table.\n\n| Field | Type |\n| --- | --- |\n| anonymous\\_id | STRING |\n| context\\_page\\_path | STRING |\n| context\\_library\\_name | STRING |\n| context\\_locale | STRING |\n| received\\_at | TIMESTAMP |\n| timestamp | TIMESTAMP |\n| context\\_user\\_agent | STRING |\n| id | STRING |\n| context\\_consent\\_opt\\_out\\_c\\_0001 | BOOLEAN |\n| context\\_consent\\_opt\\_out\\_c\\_0002 | BOOLEAN |\n| context\\_consent\\_opt\\_out\\_c\\_0003 | BOOLEAN |\n| context\\_consent\\_opt\\_out\\_c\\_0004 | BOOLEAN |\n| context\\_consent\\_opt\\_out\\_c\\_0005 | BOOLEAN |\n| context\\_page\\_url | STRING |\n| context\\_page\\_title | STRING |\n| context\\_providers\\_facebook\\_tag | STRING |\n| sent\\_at | TIMESTAMP |\n| original\\_timestamp | TIMESTAMP |\n| context\\_ip | STRING |\n| context\\_page\\_referrer | STRING |\n| user\\_id | STRING |\n| site | STRING |\n| type | STRING |\n| email | STRING |\n| integrations | STRING |\n\n* * *\n\n**Group Events**: The Group method allows you to associate a user with a single or multiple groups, with each group assigned their own unique groupId. Groups of users could represent the organization, company or account they are a part of, or any other type of group you’d like to associate with a subset of users. A Group ID can be assigned traits when this event method is called, enabling you to describe the group in more detail as well, including the name of the group, subscription type the organization has purchased, and more.\n\nHere is how Group events work end to end:\n\n1. **Send the Group event from your website/property:** Here is how you send a Group event using the Javascript SDK using Javascript on your website:\n\n```\nanalytics.group(\"example_group_id\", {\n\tname: \"Leo Burnett\",\n\tindustry: \"Advertising\",\n\temployees: 722,\n\tplan: \"premium\",\n});\n```\n\n2. **Event Processing Service processes the event**: The Javascript SDK page method will generate a Group event payload that will be sent to your **Event Processing Service**. Here is a slimmed-down version example of a payload.\n\n```\n{\n \"type\": \"group\",\n \"groupId\": \"example_group_id\",\n \"traits\": {\n \"name\": \"Leo Burnett\",\n \"industry\": \"Advertising\",\n \"employees\": 722,\n \"plan\": \"premium\"\n }\n```\n\n3. **Event Processing Service sends to Data Cloud**: The Group event payload is processed and stored in your Data Cloud in a table for consumption by GrowthLoop and can now be used in building audiences and journeys.\n\nWith your events now being sent to your Event Processing Service, you can begin routing these events to your Data Cloud. You can write events to any of the following data clouds or file storage systems:\n\n* Amazon S3\n* Amazon Redshift\n* Google Cloud Storage\n* Google BigQuery\n* Snowflake\n* DataBricks\n* Azure Blob Storage\n\nWe recommend writing events to your Data Cloud. You can then use these events in GrowthLoop by setting up a [new Dataset](https://docs.growthloop.com/docs/setup-datasets) and adding it to a Dataset Group. This will enable you to leverage events in audience and journey building.\n\nOnce events are collected and sent to the Events Processing Server, credentials are required for connecting to your Data Cloud. The example below is what is required for a connection to **BigQuery**. Other Data Cloud credentials may vary.\n\nBigQuery Connection Parameters:\n\n* **PROJECT\\_ID** - Your BigQuery Project ID\n* **DATASET** - The name of the BigQuery dataset where you want to write events\n* **REGION** - Geographic Region, this is most commonly **US**\n* **CREDENTIALS** - The credentials blob will look similar to the example below\n\n```\n{\n \"type\": \"service_account\",\n \"project_id\": \"project_id\",\n \"private_key_id\": \"privatekey\",\n \"private_key\": \"-----BEGIN PRIVATE KEY-----\\nprivatekey\\n-----END PRIVATE KEY-----\\n\",\n \"client_email\": \"generic@generic.iam.gserviceaccount.com\",\n \"client_id\": \"1111111\",\n \"auth_uri\": \"https://accounts.google.com/o/oauth2/auth\",\n \"token_uri\": \"https://oauth2.googleapis.com/token\",\n \"auth_provider_x509_cert_url\": \"https://www.googleapis.com/oauth2/v1/certs\",\n \"client_x509_cert_url\": \"https://www.googleapis.com/robot/v1/metadata/x509/generic%generic.iam.gserviceaccount.com\",\n \"universe_domain\": \"googleapis.com\"\n}\n```\n\nGrowthLoop's event collection service (in partnership with MetaRouter) works out of the box to collect all events including anonymous events and events where a user is \"known\".\n\n* **Anonymous Events:** Events that occur on your properties where you have no way of identifying the user.\n* **Known Events:** Events that occur on your properties where the email, phone, or ID of the user is known to your system.\n\nThere are two key use cases for anonymous events:\n\n1. **Linking Anonymous behavior to Known Users:** Once a user has signed up as a customer you will see all of the known events they perform. However, it is helpful to know all of the events they did prior to signing up as well so you understand their preferences better. Imagine a user that has visited your website several times and explored what they are interested in prior to every signing up. This information can prove very valuable in knowing what to recommend to them once they have signed up.\n2. **Retargeting users performing anonymous events:** It is extremely valuable to be able to retarget users based on their anonymous behavior with paid media campaigns. This capability is being severely restricted as 3rd party cookies are deprecated across the internet.\n\nWith GrowthLoop Events Service every event includes an `anonymous_id`. Once users become known (when they sign up for your service, a newsletter, or some other method), all of their events will contain their known user ids. Their previous events that contain `anonymous_id` can be used as well when building audiences to target them. Since `anonymous_id` is placed on local\\_storage, it can associate anonymous events happening from the same device up to 12 months apart.\n\nHere is how you leverage these anonymous events in GrowthLoop Audience Builder:\n\n1. Click Dataset Group in left-hand menu\n2. Create your Dataset Group\n3. Add your Known User dataset as **Primary** or **User Dataset**\n4. Add your Known Events dataset to Dataset Group\n5. Now you can target known users based on their known event behavior. But, let's extend this to include their anonymous events as well.\n6. Add your Anonymous Events dataset to Dataset Group, and join to your Known User dataset based on`anonymous_id`. This ID links your known user to any anonymous events they performed prior to becoming known.\n7. When building an audience, you can now target users based on known events they have performed, and anonymous events they performed prior to setup in the same place.\n\nCongratulations, you can now target customers and provide recommendations for products and services based on their browsing behaviors prior to signing up and becoming known users.\n\nWith the **Advanced Events Collection Service**, GrowthLoop can add additional targetable keys to every anonymous event. Each event written to your data cloud starts with an `anonymous_id`.\n\nAdvanced Events expands on this `anonymous_id` and enriches the anonymous profile with IDs from key social and paid media network profiles including Pinterest, Facebook, Ticktock, Trade Desk and more.\n\n![](https://files.readme.io/1ac1ec1-anonymous_profile.png)\n\nHere is the full list of enrichment IDs that can be included on the user profile:\n\n* Acuity Ads\n* Adobe Analytics\n* Amnet\n* Amobee\n* Appsflyer\n* Bloomreach\n* Criteo\n* Facebook Pixel\n* Google Ads\n* Impact Radius\n* InMarket\n* MediaMath\n* Merkle\n* Moveable Ink\n* NextDoor\n* Pinterest\n* Revjet\n* Snapchat\n* The Trade Desk\n* Twitter\n* Verizon Media\n* Xandr\n\nOnce the anonymous profile is enriched with these IDs, they can then be used to target anonymous users across these paid media platforms using GrowthLoop's Audience Builder. Here is how:\n\n* With **Advanced Events Service**, you can create an audience builder in GrowthLoop dedicated to targeting anonymous visitors to your properties.\n* Start by setting up a Dataset Group for anonymous users in GrowthLoop to begin creating audiences and journeys to target anonymous users with paid media.\n* Setup your [Dataset Group](https://docs.growthloop.com/docs/setup-dataset-group) and include your anonymous profile dataset as primary dataset.\n* Add your anonymous [events dataset](https://docs.growthloop.com/docs/setup-datasets#create-dataset) to the dataset group.\n* Create an audience of anonymous users based on their event behavior.\n* When exporting audiences to end platforms like Facebook Ads or TradeDesk, utilize their anonymous profile id for that destination as a match key.\n\nCongratulations, you can now target anonymous users browsing your properties across paid media channels directly from GrowthLoop.\n\nHave any questions about modifying your journeys? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and our dedicated solutions architects will be able to help.\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:22.677Z","d17720b7-60ac-47de-9b42-a477be06a763",[],[],{"_40":654,"_128":655,"_130":656,"_132":657,"_134":-5,"_13":-5,"_120":658,"_122":136,"_25":659,"_138":-5,"_139":660,"_141":661},"How to connect Braze and create Syncs | GrowthLoop Docs","how-to-connect-braze-and-create-syncs-growthloop-docs","https://docs.growthloop.com/docs/braze-syncs","# How to connect Braze and create Syncs\n\nEnhance your Braze campaigns with powerful customer data from your data warehouse.\n\nIn this guide, we’ll walk you through syncing customer data from your data warehouse into Braze to supercharge your marketing efforts. Let's get started!\n\nGrowthLoop enables syncing to these Braze objects:\n\n| Object | Description | Sync Modes | Field Mappings (Required) | Field Mappings (Optional) |\n| --- | --- | --- | --- | --- |\n| `Event` | Sync and track in-app behaviors, such as clicks, page views, or interactions | Insert (adds new events) | `Event name`: The event’s name

`Timestamp`: When the event occurred | |\n| `Profile Attribute` | Update user preferences and attributes for personalized campaigns | Insert (adds new profiles)

Update (modifies existing profiles)

Upsert (combines insert and update) | At least one attribute, e.g., `Country` | |\n| `Purchase` | Sync transaction data for targeting users with offers or promotions | Insert (adds new purchase records) | `Product ID`: Identifier, e.g., Product Name

`Price`: Amount paid

`Time`: When the purchase occurred,

`Currency`: e.g., USD | `Quantity`: Purchased amount |\n\n> 📘\n> \n> You can sync JSON objects and object arrays to Braze `Profile Attributes`. The data passed from your warehouse must be stored as a **string** - GrowthLoop will automatically convert that string to JSON during export.\n> \n> In Braze, create the custom attribute first. Choose **Object** for a single JSON object, or **Object Array** for an array of JSON objects.\n> \n> **Example structure of column values in your warehouse:**\n> \n> * **Single JSON object:** `'{\"city\":\"Abilene\",\"state\":\"Texas\",\"zip_code\":79605}'`\n> * **Array of JSON objects:** `'[{\"city\":\"Abilene\",\"state\":\"Texas\"}, {\"city\":\"Austin\",\"state\":\"Texas\"}]'`\n\n* Create a **Braze API Key**.\n 1. Log in to Braze and go to **Settings > APIs and Identifiers**.\n 2. Click **Create API Key**, name it \"GrowthLoop,\" and select the `User Data`, `Purchases`, and `Events` permissions.\n 3. Click **Create API Key** again to save your configuration. Make sure to copy the **Identifier**, as you'll need it for the next step.\n* Locate your **Braze API URL**. Visit [Braze endpoint documentation](https://braze.com/docs/api/basics/#endpoints) to locate the API URL for your Braze instance. Be sure to copy the full API URL (i.e., REST Endpoint).\n\n> 📘\n> \n> If your Braze URL is [https://dashboard-06.braze.com](https://dashboard-06.braze.com/), your API URL (i.e. REST Endpoint) will be [https://rest.iad-06.braze.com.](https://rest.iad-06.braze.com./)\n\n1. To begin, sign into the GrowthLoop Platform and navigate to the **Destinations** tab on the left sidebar. Click **New Destination** in the top right corner.\n2. In the **Select Destination** window that pops up, type **Braze** into the search bar to find Braze. Click **Add Braze**.\n3. Clicking **Add Braze** will require you to select/insert the following information:\n 1. **Destination Name:** The name that will be used for this destination in the app.\n 2. **Sync Frequency:** Choose either `Daily` or `Hourly,` which will determine how often GrowthLoop exports audiences to Braze.\n 3. **API Key:** Enter the \"Identifier\" of your API Key from Braze.\n 4. **API URL:** Enter the full API URL (i.e., REST Endpoint).\n4. Click **Create**. We’ll validate your permissions to ensure we can load your customer data to Braze. If successful, Braze will appear in your list of connected destinations!\n\n1. Navigate to the **Syncs** tab on the left sidebar and click **Create Sync** in the top right corner.\n2. Set up your Sync with the following details:\n 1. **Sync Name:** A clear, friendly name for your sync.\n 2. **Sync Frequency:** How often data should sync to the destination.\n 3. **Update Rule:** The default method for syncing data to the destination.\n 4. **Dataset / Table:** The table containing your events, purchases, or user data.\n 5. **Match Field:** The column used to identify users in your source table for the destination system.\n 6. **Dataset Unique Field:** The column with unique values for each user in the table.\n 7. **Connection:** Choose the destination for syncing data. Select **Braze**.\n 8. **Object Type:** Choose the data object to sync: `Event`, `Purchase`, or `User Attribute`.\n 9. **Match Field:** The column used to match and identify users in the destination system based on your source data.\n3. Once you finish selecting/inserting the required fields, click **Save Sync.**\n4. Next, you'll need to add field mappings based on the object you're syncing to. In this case, we're syncing to the `Event` object, which requires the following:\n 1. `Event Name`: The name of the event. See best practices on naming conventions [here](https://www.braze.com/docs/user_guide/data_and_analytics/custom_data/event_naming_conventions/#properties).\n 2. `Event Time`: Indicates when the event occurred. Make sure it is in ISO 8601 or in yyyy-MM-dd'T'HH:mm:ss:SSSZ format.\n5. To map the fields, select the column that represents the `Event Name` from the drop-down under **Source**.\n6. Under the **Destination** section, select **Event Name** from the drop-down.\n7. Click **Add Mapping** to include a new **Source -> Destination** row underneath.\n8. Repeat steps 5 through 7 to map the remaining required destination field: `Event Time`\n\n> 📘\n> \n> **Object** or **Object Array** attributes created in Braze will not appear as selectable values in the destination drop-down. To sync to these attributes, manually enter the attribute name exactly as it appears in Braze, then map the source column containing the JSON-formatted data as usual. When manually entered, the attribute name may appear in the drop-down as “undefined” - this is expected and does not affect functionality.\n\n9. After mapping all the fields, clicking **Update Sync** will prompt you with the following two options:\n 1. **Updates Only**: We recommend you go with the this option, especially if you’re setting up the sync for the first time.\n 2. **Back-fill**: This option is when you are updating an existing Sync with newly mapped fields and you’d like all your **already synced events** to have those fields backfilled for them. This operation can be very expensive and time consuming on your underlying Data Warehouse, so please choose that option if you’re absolutely sure.\n10. Finally, click the **toggle** at the top of the page to enable!\n11. To view your event data in Braze, navigate to the **Audience** section, select **Search Users**, search for a specific user, and scroll down to the **Custom Events** section.\n\n![](https://files.readme.io/3f2be26-image.png)\n\n> 👍\n> \n> You have successfully created an `Event` sync to Braze!\n\n> 📘\n> \n> Experiencing any issues configuring Syncs to Braze? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and we’ll be in touch shortly!\n\nUpdated 16 days ago\n\n* * *\n\nWant to discover more ways to combine GrowthLoop and Braze? Click below for a full list of use cases!\n\n* [Integrate with Braze](https://docs.growthloop.com/docs/integrate-braze)","2025-06-20T22:58:03.763Z","173753ee-3134-4481-9130-a2db5c3d0936",[],[],{"_40":663,"_128":664,"_130":665,"_132":666,"_134":-5,"_13":-5,"_120":667,"_122":136,"_25":668,"_138":-5,"_139":669,"_141":670},"How to copy an audience in GrowthLoop | GrowthLoop Docs","how-to-copy-an-audience-in-growthloop-growthloop-docs","https://docs.growthloop.com/docs/copy-an-audience","# How to copy an audience in GrowthLoop\n\nHave an idea for a new audience but don’t want to rebuild from scratch? In this tutorial, you’ll learn how to make a copy of an existing audience and modify it to your liking. You might choose to do this to create lookalike audiences, or adjusting filters slightly for fine-tuning of your audience, or maybe create audiences for future inclusion and exclusion audiences.\n\n1. Navigate to **Central Audience Hub** by clicking **Audiences** under **Platform** in the GrowthLoop app. Then, select the audience you want to copy.\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd84845d81cb56_REbZGPPaQ4dGqMK6T4SXADRr1bn4eHsExt5k4ZcwVI1ZjQZz5Bf-q2udcke_r1K7ovB1jbNXX73Z5iJAONiGM4tqKPu0GXH8NGE7yP9SKFNXHgIw9CIsQerGs8eiM_yBj7IQRQ38kzKhu5Bjl_H9SINuzw%3Ds2048.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd84845d81cb56_REbZGPPaQ4dGqMK6T4SXADRr1bn4eHsExt5k4ZcwVI1ZjQZz5Bf-q2udcke_r1K7ovB1jbNXX73Z5iJAONiGM4tqKPu0GXH8NGE7yP9SKFNXHgIw9CIsQerGs8eiM_yBj7IQRQ38kzKhu5Bjl_H9SINuzw%3Ds2048.png)\n\n2. Click **the Export drop-down button below your customer count and select Copy**.\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd84e9c481cb66_FFwgjHUEFwxDMRcZOU2nnffGvgdmzndOrY28ngwJEsyUgBRpDKnFIe9I9xRq3SCDO9kVlhwMNmxDmvIuqN4Azpfzq9QMxFpy5Sg75ICIz0JPzx92NR5bn1WEDtcbMZYN8HUle6avnpio_ftiaz0GdpFEmg%3Ds2048.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd84e9c481cb66_FFwgjHUEFwxDMRcZOU2nnffGvgdmzndOrY28ngwJEsyUgBRpDKnFIe9I9xRq3SCDO9kVlhwMNmxDmvIuqN4Azpfzq9QMxFpy5Sg75ICIz0JPzx92NR5bn1WEDtcbMZYN8HUle6avnpio_ftiaz0GdpFEmg%3Ds2048.png)\n\n‍\n\n3. A new audience template will appear with all your filters copied over. Once you title your audience, it will begin saving. Make sure you name your audience accordingly so that you know the difference between this audience and the original.\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd8482db81cb68_LasygMnh6L0U7bIwzgHXjo5BaP2tD7oi4D8exhisygOYXWdlju0oOGIQIqRGKwNhIML7OLXIk3Uhilu3mOCYKKfqh9E6UwlLHPxaHljqXr3lWpBhFn1N9VFUbw4g4p6gl6J9TKa0aXWhUJPfIS9GK2uNmw%3Ds2048.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd8482db81cb68_LasygMnh6L0U7bIwzgHXjo5BaP2tD7oi4D8exhisygOYXWdlju0oOGIQIqRGKwNhIML7OLXIk3Uhilu3mOCYKKfqh9E6UwlLHPxaHljqXr3lWpBhFn1N9VFUbw4g4p6gl6J9TKa0aXWhUJPfIS9GK2uNmw%3Ds2048.png)\n\n4. Then, create your audience as you would a new audience, adding relevant filters for your target audience. Visit **[Create an Audience](https://docs.growthloop.com/docs/create-an-audience)** if you need a refresher on how you can build an audience.\n\nWant to learn how to export your audience to Facebook, Adwords, or other destination platforms? Go to the [Destinations](https://www.growthloop.com/help-center-categories/destinations) category to see how.\n\nIf you need any other help, visit our **[help center](mailto:/help-center)** or reach out to **[support@growthloop.com](mailto:support@growthloop.com)**\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:25.762Z","9b748d0c-e143-4fd9-af0f-5fac0a89b16d",[],[],{"_40":672,"_128":673,"_130":674,"_132":675,"_134":-5,"_13":-5,"_120":676,"_122":136,"_25":677,"_138":-5,"_139":678,"_141":679},"How to create a conversion sync to Pinterest | GrowthLoop Docs","how-to-create-a-conversion-sync-to-pinterest-growthloop-docs","https://docs.growthloop.com/docs/pinterest-conversions","# How to create a conversion sync to Pinterest\n\n## Pinterest Conversions\n\nLearn how to send conversion events to Pinterest Ads via Growthloop\n\nIn this article, we'll walk you through syncing conversion events to `Pinterest` for a more comprehensive view of your campaign performance. Let's get started!\n\nGrowthLoop enables syncing to the following Pinterest object:\n\n| Object | Description | Sync Modes | Field Mappings (Required) | Field Mappings (Optional) |\n| --- | --- | --- | --- | --- |\n| `Conversion` | Sync and track web, in-app, and offline behaviors | Insert (adds new events) | `Action Source`: Where the conversion event occurred, such as web, offline, etc

`Event Name`: The type of the user event, such as checkout, page\\_visit, search, etc

`Event ID`: The unique id string that identifies the event

`Event Time (timestamp)`: The time when the event happened in Unix format

`User Data`: At least one piece of user data for matching, like hashed email or or both Client IP Address and Client User Agent | See full list of parameters [here](https://developers.pinterest.com/docs/api/v5/events-create/) |\n\n* Have a `Pinterest Ads Manager` account. Create one [here](https://help.pinterest.com/en/business/article/create-an-advertiser-account)!\n* Created a `Conversion Access Token`. To create one, open the main dropdown in the upper left corner, click `Conversions` under `Manage Business`, then click `Set up API` under `Conversion API`, and finally, select `Generate New Token`.\n\n1. To begin, sign into the GrowthLoop Platform and navigate to the `Destinations` tab on the left sidebar. Click `New Destination` in the top right corner.\n \n2. In the `Select Destination` window that appears, just type `Pinterest` into the search bar. Then, click `Add Pinterest`.\n \n3. In the window, please enter the following information to set up the connection to the destination.\n \n * `Destination Name`: This is how the destination will be named and referred to in the app going forward.\n * `Sync Frequency`: Choose between `Hourly` or `Daily` to determine how frequently GrowthLoop exports audiences to `Pinterest`.\n * `Select Ad Account`: Choose the account where you would like to receive GrowthLoop audiences.\n * `Conversion Access Token`: Enter your `Conversion Access Token` here to send conversion events to Pinterest Ads.\n * `Access & Refresh tokens`: These tokens are automatically generated when you authorize the app.\n4. Once you've entered the information, click on `Create`. We'll check to make sure we have all the necessary permissions to send audience data to `Pinterest`. If everything is in order, you'll now find the new `Pinterest` Destination in your list of connected destinations.\n \n\n5. To route the latest conversion events (e.g., web, in-app, offline) to `Pinterest`, go to the `Syncs` tab on the left sidebar and click `Create Sync` in the top right corner.\n6. Clicking `Create Sync` will require you to select/insert the following information:\n 1. Route Name:\n 1. **Name**: A friendly name for the signal route.\n 2. **Sync Frequency**: The default frequency for syncing the latest conversion info to a destination.\n 3. **Update Rule**: The default operation for syncing the latest user info to a destination. Pinterest supports only the `Insert` rule, which means new data is added to the destination without updating or overwriting existing data.\n 2. Source:\n 1. **Source Dataset/Table**: The table that holds the latest user info. Usually, it's organized within an `Events` table.\n 2. **Dataset Unique Field(s)**: The column that contains values that are distinct for each user in the table.\n 3. **Match Field**: The column used to match and identify users from your source table in the destination system. Please select the column that contains either `MAID`, `Hashed Email`, `Client IP Address`.\n 3. Destinations:\n 1. **Connection**: The destination you will sync data to. Please select the Pinterest destination you set up in the previous step.\n 2. **Object Type**: The object you want to send data to. Please select `Conversion Event`.\n 3. **Match Field**: The column used to match and identify users from the destination system in your source table. Depending on what you selected as your `Source Match Field`, choose `MAID`, `Hashed Email`, or `Client IP Address`.\n7. Once you finish selecting/inserting the required fields, click `Save Route`**.**\n8. It's time to add the field mappings to activate your signal route. The following fields are required: `Action Source`, `Event Name`, `Event ID`, and `Event Time (timestamp)`. In addition, you must select either `Emails` or `Hashed MAID (List)` or both `Client IP Address` and `Client User Agent`.\n9. To map the fields, navigating to the `Field Mapping` section. Choose the columns that correspond to the required `Destination Fields` from the drop-down menu under `Source`.\n10. To include extra mappings for the other fields, click on `Add Mapping`. This will generate a new row for `Source > Destination`.\n11. Look for and choose the fields in your source table for the remaining items.\n12. Finally, click the `toggle` at the top of the page to enable the sync!\n\n> 👍\n> \n> You have successfully created a conversion sync to `Pinterest`!\n\nTo confirm that your event data has been received, log in to your Ads account, navigate to the **Account Overview** menu and select **Conversions** under **Business**.\n\n![](https://files.readme.io/988d2db06ca0640ab7a699d771407391665df36a7ee32351e08016c09e5990b0-image.png)\n\n> 📘\n> \n> If you experience any issues when connecting to or creating syncs to Pinterest Conversions, please reach out to us at [support@growthloop.com](mailto:support@growthloop.com), and we’ll be in touch shortly to help resolve the matter!\n\nUpdated 5 months ago\n\n* * *","2025-06-20T22:58:02.377Z","7d1e3268-066f-4fe6-b40c-927333e12655",[],[],{"_40":681,"_128":682,"_130":683,"_132":684,"_134":-5,"_13":-5,"_120":685,"_122":136,"_25":686,"_138":-5,"_139":687,"_141":688},"How to create a CRM Journey | GrowthLoop Docs","how-to-create-a-crm-journey-growthloop-docs","https://docs.growthloop.com/docs/crm-journeys","# How to create a CRM Journey\n\n## CRM Actions\n\nLearn how to create a journey that bridges marketing and sales\n\nIn this article, you'll learn how to take actions in your CRM directly from a GrowthLoop journey. This is useful for account based marketing campaigns when you would like to get your sales team to take action and follow up with contacts and leads.\n\n1. **Lead Form Routing:** Create a sequence of marketing and sales actions after a new prospect fills in a web for. For example, send them an email campaign, and if they open the email, then create a lead in your CRM with a task for a sales rep to reach out to them.\n2. **Nurture Campaigns**: Marketing is often sending a sequence of newsletters and messages to prospects. As soon as those prospects open an email or hit a certain lead score, you can route a task for sales representatives to reach out over the phone.\n\n \n\n* **CRM Match Object:** This is the object in your CRM you would like to match users in your journey with. If a user in your journey matches the object in your CRM, you can take action on them in your CRM. Here are the types of objects you can take action on in a CRM Action node.\n * Account\n * Contact\n * Lead\n * Opportunity\n* **CRM Action:** GrowthLoop enables you to take action on users in your journey that match with your CRM. You can perform the following actions:\n * **Create Activities:** This action enables you to create activities on the match object. This is great for providing activities for your sales team on specific leads, contacts, or accounts. For example, when a Lead hits a certain score you can route a task for the assigned sales rep to reach out to that Lead. Here are the types of activities you can create:\n * Call\n * Email\n * Meeting\n * Task\n * **Create Opportunity:** This action enables you to create an opportunity on the matching object. For example, if a customer fills in a form interested in a new service, you can create an opportunity on that contact in your CRM. _Note: This action is only available on`Accounts` and `Contacts` objects._\n * **Map to Campaign**: This action enables you to map CRM objects to a specific campaign in your CRM. This is often used for tracking purposes. For example, if you are running a conference event and you want all leads generated from the conference to be associated with a campaign in your CRM, you can now easily map them to that campaign in a GrowthLoop journey. This would enable you to track exactly how your conference performed directly in your CRM reports.\n\n \n\n1. Create new Journey\n2. Drag CRM Action Node from Library onto Journey Canvas\n\n![](https://files.readme.io/5a6d437eb714773308f8279bcd087362ae82d901756250f51e02bef001bebe79-crm_action_node.png)\n\n3. Click on CRM Action Node to start configuration\n4. Select the CRM Object you would like to take action on. For example, if your entry audience contains new leads from a web form on your website, you will want to match those new leads to Leads in your CRM, and then take action on them by creating a task for your sales reps. \\_Note: you will not take action on users that do not match existing objects in your CRM. You can match users in your journey to any of the following CRM objects:\n 1. Account\n 2. Contact\n 3. Lead\n 4. Opportunity\n\n![](https://files.readme.io/5abee3a408a1a6fb0a819798003f5f534258cb57959dc3b91c10781a64542f14-object_match.png)\n\n5. Click Next\n6. Select how you would like to match users in your journey to the CRM Match object. Each user that flows through your journey will be matched to the CRM Object on a field that you specify.\n 1. Select Field in source: This is the field in your primary dataset you'd like to use for users entering your journey to match on with CRM.\n 2. Select Field in CRM: This is the field on your CRM object you would like to match users in your journey with. \n _Note: This will determine whether there is a matching Lead/Contact/Account/Opportunity in your CRM to take action on._\n7. Select the Action you want to take on the CRM object. You can:\n 1. Create Activities\n 2. Create Opportunity (only for Account and Contact objects)\n 3. Map to Campaign\n\n![](https://files.readme.io/28d6b4dd0faabb842e25426d54a32c2696353fb6174221f7bd7096cc066a33c5-take_action2.png)\n\n1. If you select `Create Activities` you can specify the `Activity Type`:\n 1. Call\n 2. Email\n 3. Meeting\n 4. Task\n\n![](https://files.readme.io/1bdb3a8a6b68eb2707e2e5a315564ceda40d7dc93670483499b613a082e11db7-image.png)\n\n2. Once you select an `Activity Type`, you can specify details for that activity. Your sales reps will receive all the details you provide on your activity to help them take action.\n 1. Activity Name\n 2. Activity Comment\n 3. Activity Due Date\n 4. Activity Owner: For Activity Owner, you are able to specify a specific owner from your CRM for all the activities. Or, you can specify that the new Activity should be assigned to the current owner of the Contact/Lead/Account.\n\n![](https://files.readme.io/41f3e38aa002b60d95b1234ac58f94d4dad1e1b46f6b237ce5b40a9d865f8394-create_task.png)\n\n3. Click Save\n4. Publish your journey\n5. Now, every user in your journey that reaches the CRM Action node, and matches your CRM object, will have a new Activity created for them directly in your CRM system.\n\n \n\n1. If you select `Create Opportunities` as your CRM Action, you can provide details on the opportunity that will be created for your sales reps.\n2. Provide Name of the Opportunity. This will help your sales reps understand what type of opportunity you are creating for their `Contacts` or `Accounts`\n3. Provide Amount of Opportunity (optional). This can help inform sales reps of the estimated amount the opportunity is worth. This helps sales reps prioritize which opportunities they pursue in CRM.\n4. Provide Opportunity Close Date (optional). This is an estimate on when it is believed the opportunity will be closed or signed.\n5. Provide Opportunity Owner. You can specify a specific owner from your CRM for all the opportunities created. Or, you can specify that the new Opportunity should be assigned to the current owner of the Contact/Account.\n\n![](https://files.readme.io/7fe3541a3ed70ad236a4a58d358e0371f396a02177703797d37d56b40c0cb21f-create_opportunity.png)\n\n1. If you select `Map to Campaign` as your CRM Action, you can specify which campaign to map your contacts, leads, accounts, or opportunities to.\n2. Select `Campaign Type` you would like to map users in the journey to. You can map users to a `New Campaign` or `Existing Campaign`\n3. If you select `New Campaign` you can specify the campaign name. This will create a new campaign and map users to it once the journey is published.\n\n![](https://files.readme.io/55433abfa58d097872f98e93e3eb2e9e28439d054c025123c7db3acda92c9374-new_campaign.png)\n\n4. If you select `Existing Campaign` you can select an existing campaign that already exists in your CRM and users in the journey will be added to it.\n\n![](https://files.readme.io/ffe112c8c7661eabde4c1b2960df5156c629b5f6eda9524f7096e5984f310928-existing_campaign.png)\n\nWith GrowthLoop Journeys you can sequence a number of CRM actions to create a waterfall workflow in your CRM. Imagine you would like to create a Task on New Leads for your sales reps to reach out, and then would like to map them into your \"Lead Capture\" campaign in your CRM. You can do this easily by chaining CRM Actions into an `Action Sequence`.\n\n1. Create your first CRM Action node to create a Activity on new Leads\n2. Drag a second CRM Action node onto Journey Canvas\n3. Connect second CRM Action node to your Activity Creation Action Node to the `Match` or `Green` connector.\n4. Configure your second CRM Action Node to Map to Campaign.\n\n![](https://files.readme.io/4c0479dbd7a9b172ea71d33f650dfedd08f75530cc421df1764e695b3df3c479-action_sequence.png) ![](https://files.readme.io/0eec9fcb31237554f52ca20f3073cde6c2c5d3fa18d65be146818dc0e8ebe945-action_sequence.png)\n\nSequencing CRM Actions into a waterfall can be a very powerful tool to build workflows in CRM that help orchestrate your marketing with your sales team, and also make tracking the performance in campaigns trackable directly within your CRM.\n\nHave any questions about CRM Action nodes? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com).\n\nUpdated 5 months ago\n\n* * *\n\n* [Data Cloud Storage](https://docs.growthloop.com/docs/journey-state-tables)\n* [Monitor a Journey](https://docs.growthloop.com/docs/journey-monitoring)","2025-06-20T22:58:18.740Z","b90a2625-f5f1-4962-a2b7-1d1493ebc1b3",[],[],{"_40":690,"_128":691,"_130":692,"_132":693,"_134":-5,"_13":-5,"_120":694,"_122":136,"_25":695,"_138":-5,"_139":696,"_141":697},"How to create and configure Dataset Groups | GrowthLoop Docs","how-to-create-and-configure-dataset-groups-growthloop-docs","https://docs.growthloop.com/docs/setup-dataset-group","# How to create and configure Dataset Groups\n\n## Set Up Dataset Groups\n\nLearn how to setup your first Audience Builder with Dataset Groups.\n\nIn this article, you'll configure your first `Dataset Group` in GrowthLoop so your business teams can begin creating audiences and journeys.\n\nDataset Groups are a way to group a set of tables or models in GrowthLoop that business teams can use for building audiences and journeys. For example, you may have a customers table associated with a purchases table based on customer\\_id. You can add both the customers table and purchases table to the same `Dataset Group` in GrowthLoop so they can both be used together when creating audiences or journeys.\n\n![](https://files.readme.io/82a021c-Screenshot_2024-01-24_at_11.41.48_AM.png)\n\nEach time a user on your team creates an audience or journey they will be asked what `Dataset Group` they would like to use. Once they select a `Dataset Group`, they can use all the data within those tables while building their audience.\n\n![](https://files.readme.io/8cd49ee-dataset_group_selection.png)\n\nMany customers create `Dataset Groups` for each line of business. For example, they may have a `Dataset Group` for `B2B Customers` that has Accounts and Purchases table. Separately, they may have a `Dataset Group` for `Consumer Customers` that has a Customers and Events table. Administrators can then select who within your team has access to build audiences or journeys on each of the `Dataset Groups`\n\n1. Navigate to `Datasets` in the left menu rail\n2. You can see all `Dataset Groups` your team has created\n3. Select `New Dataset Group`\n\n![](https://files.readme.io/17bba2b-dataset_group_primary.png)\n\n1. **Group Name:** This is the name of your `Dataset Group` that will be visible to other users on your team. Every time a teammate creates a new audience or journey they will be able to select `Dataset Group` and will see this name. We recommend putting in a name others in your organization will recognize.\n \n2. **Group Description:** Insert a group description so others on your team will know what area of your business this `Dataset Group` is most useful for when creating Audiences and Journeys.\n \n3. **Select Primary Dataset**: Select a `Dataset` that will serve as your `Primary` dataset. This is typically a users or customers dataset that you are planning to building audiences with and export.\n \n4. **Configure Personalizations (Optional)**: Select fields from your `Primary Dataset` that you want to have as default personalization fields for every audience and journey created using this `Dataset Group`. This is just a simple way to make it easy for users to include specific fields when exporting an audience.\n \n5. Click Create\n \n\n \n\n1. Navigate to the dataset you want to add to your **Dataset Group**\n2. Open up the dataset and scroll to the bottom to the **Join Configuration** section\n3. Select your **Dataset Group** you would like to add this **Dataset** to from the **Dataset Group** dropdown.\n4. Select the table within the **Dataset Group** you would like to join the dataset to.\n5. Select the join relationship\n 1. One to One\n 2. One to Many\n 3. Many to One\n 4. Many to Many\n 5. **Having trouble choosing?**: The helpful info icon will explain exactly how your datasets will be joined together so you can use it as your guide to confirm you will achieve your desired outcome.\n6. Select the keys from each dataset you would like to perform the join on.\n7. You can add multiple join keys by selecting \"Add Join Key\" if you would like to join the datasets on multiple columns.\n8. Save your Dataset.\n\n![](https://files.readme.io/ca26c74-advanced_joins_tooltip.png)\n\n1. Select `Audiences` in left menu rail\n2. Select `New Audience`\n3. Select your new `Dataset Group`\n\n![](https://files.readme.io/88d629b-Screenshot_2024-01-23_at_2.00.13_PM.png)\n\n4. Select `Start with the Basics`\n5. Build your audience!\n\n![](https://files.readme.io/46ed18d-build_audience_dataset_group.png)\n\n* * *\n\n> 👍\n\nYour dataset group can now be used to create:\n\n* [Audiences:](https://docs.growthloop.com/docs/audiences-overview) Must add your dataset to a specific `Dataset Group`\n* [Journeys](https://docs.growthloop.com/docs/journeys-overview) Must add your dataset to a specific `Dataset Group`\n\nDataset Groups were designed to be flexible and be able to map to any enterprise schema in the data cloud. Our goal is to \"Meet you where your data is today\". With that in mind, here are several use case examples of Dataset Groups setup by customers.\n\nA very common schema pattern is to have events or transaction tables without much information on them. The schema has been normalized so an events table may just have event\\_id and timestamp and not much else. The actual attributes of the events live on a separate table. However, your team will want to build audiences on all events of a certain category and value. So, how do you enable this?\n\n![](https://files.readme.io/a73a15a-event_metadata.png)\n\n**Adding Metadata filters to Events**\n\n1. Create **Dataset Group**\n2. Select your **Users** as a **Primary Dataset**\n3. Create your **Events Dataset**\n4. Add it to your **Dataset Group** through a **one to many** join with **Users Dataset**.\n5. Create your **Event Information Dataset**\n6. Add it to your **Dataset Group** through a **many to one** join with **Events Dataset**.\n\nIt's that simple. Now your business teams can build audiences and journeys based on event attributes stored in the event information while filtering your events.\n\nAnother common scenario is when data teams have to perform multiple one to many joins to get to useful information. Take the example of an e-commerce schema. Users make purchases, but each of those purchases can have multiple products within them. So, if you want to know how many customers bought Nikes, you actually want to filter on the products they've bought in addition to the Cart object. So, how would you do this?\n\n![](https://files.readme.io/2962f21-nested_joins.png)\n\n**Adding Multiple One to Many Joins**\n\n1. Create **Dataset Group**\n2. Select your **Users** as a **Primary Dataset**\n3. Create your **Carts Dataset**\n4. Add it to your **Dataset Group** through a **one to many** join with **Users Dataset**.\n5. Create your **Product Line Items**\n6. Add it to your **Dataset Group** through a **one to many** join with **Carts Dataset**.\n\nIt's that simple. Now your marketing teams can filter on everyone has spent more than $500 on products with brand \"Nike\".\n\nA common usage pattern of GrowthLoop at B2B companies is for Account Based Marketers to build audiences of users while using information at the company or account level. For example, an account based marketing may want to target all customers that work at companies in the automotive vertical. Or they may want to target all users that work at accounts that are high spenders. So, how would you do this?\n\n![](https://files.readme.io/6e98632-b2b_accounts.png)\n\n**Adding B2B Accounts Objects**\n\n1. Create **Dataset Group**\n2. Select your **Users** as a **Primary Dataset**\n3. Create your **Accounts**\n4. Add it to your **Dataset Group** through a **one to many** or **many to many** join with **Users Dataset**.\n5. Create your **Purchases** dataset\n6. Add it to your **Dataset Group** through a **one to many** join with **Users Dataset**. Note, if your Purchases or events datasets have an account\\_id, you could also join this **Purchases** dataset to **Accounts** to filter to users that belong to accounts that have exhibited certain purchases behavior.\n\nIt's that simple. Now your marketing team can build audiences targeting users that belong to accounts that exhibit certain attributes.\n\nThese use cases are just the beginning of what is possible. With **Flexible Schemas** in **Dataset Groups** can design your Audience Builder to fit your data in hundreds of ways. The goal is to \"meet you where your data is today\", so you can get up and running and give your marketing teams a powerful audience and journey canvas.\n\n* * *\n\nExperiencing any issues with GrowthLoop? Reach out to us at **[support@growthloop.com](mailto:support@growthloop.com)** and we’ll be in touch shortly!\n\nUpdated 5 months ago\n\n* * *\n\n* [Audiences](https://docs.growthloop.com/reference/audiences)","2024-03-20T21:02:23.834Z","a0b20b1e-004e-4875-8092-30b897230cf2",[],[],{"_40":699,"_128":700,"_130":701,"_132":702,"_134":-5,"_13":-5,"_120":703,"_122":136,"_25":704,"_138":-5,"_139":705,"_141":706},"How to create signal Syncs for Iterable | GrowthLoop Docs","how-to-create-signal-syncs-for-iterable-growthloop-docs","https://docs.growthloop.com/docs/iterable-sync","# How to create signal Syncs for Iterable\n\nEnhance your Iterable campaigns with powerful customer data from your data warehouse.\n\nIn this guide, we’ll walk you through syncing customer data from your data warehouse into Iterable to enhance your customer engagement. Let's get started!\n\nGrowthLoop enables syncing to these Iterable objects:\n\n| Object | Description | Sync Modes | Field Mappings (Required) | Field Mappings (Optional) |\n| --- | --- | --- | --- | --- |\n| `Event` | Sync and track specific customer actions, such as clicks, page views, or interactions, within the platform | Insert (adds new event)

Update (modifies existing events)

* Upsert (combines insert and update) | `Event Name`: Name of the event

AND

`Email` or `User ID`: Specify either the email associated with the user’s profile or the unique ID for the user profile in Iterable | `Event ID`: The unique ID for the event. Specify this ID in the field mapping if you want to update an existing event

`Campaign ID`: Campaign tied to conversion

`Template ID`: Template tied to the conversion |\n| `User` | Create, enrich, and update users with any additional information you define | Insert (adds new profiles)

Update (modifies existing profiles)

Upsert (combines insert and update) | `Event Name`: A unique identifier for a specific customer action

AND

`Email` or `User ID`: Specify either the email associated with the user’s profile or the unique ID for the user profile in Iterable | |\n\n* To set up Syncs in Iterable, ensure you have an active Iterable account and have configured it as a destination. Click [here](https://docs.growthloop.com/docs/iterable) to learn how.\n\n1. Navigate to the **Syncs** tab on the left sidebar and click **Create Sync** in the top right corner.\n2. Set up your Sync with the following details:\n 1. **Sync Name:** A clear, friendly name for your sync.\n 2. **Sync Frequency:** How often data should sync to the destination.\n 3. **Update Rule:** The default method for syncing data to the destination.\n 4. **Dataset / Table:** The table containing your events or user data.\n 5. **Match Field:** The column used to identify users in your source table for the destination system.\n 6. **Dataset Unique Field:** The column with unique values for each user in the table.\n 7. **Connection:** Choose the destination for syncing data. Select **Iterable**.\n 8. **Object Type:** Choose the data object to sync: `Event` or `User`\n 9. **Match Field:** The column used to match and identify users in the destination system based on your source data.\n3. Once you finish selecting/inserting the required fields, click **Save Sync.**\n4. Next, you'll need to add field mappings based on the object you're syncing to. In this case, we're syncing to the `Event` object, which requires the following:\n 1. `Event Name`: A distinct identifier for a specific customer action, which can be either a standard event like “Subscribe” or custom event.\n 2. `Email` or `User ID`: Specify either the email associated with the user’s profile or the unique ID for the user profile in Iterable.\n5. To map the fields, select the column that represents the `Event Name` from the drop-down under **Source**.\n6. Under the **Destination** section, select **Event Name** from the drop-down.\n7. Click **Add Mapping** to include a new **Source -> Destination** row underneath.\n8. Repeat steps 5 through 7 to map the remaining required destination field: `Email` or `User ID`\n9. After mapping all the fields, clicking **Update Sync** will prompt you with the following two options:\n 1. **Updates Only**: We recommend you go with the this option, especially if you’re setting up the sync for the first time.\n 2. **Back-fill**: This option is when you are updating an existing Sync with newly mapped fields and you’d like all your **already synced events** to have those fields backfilled for them. This operation can be very expensive and time consuming on your underlying Data Warehouse, so please choose that option if you’re absolutely sure.\n10. Finally, click the **toggle** at the top of the page to enable!\n11. To view your event data in Iterable, go to the **Audience** section, select **User Lookup**, search for a specific user, and then choose the **Events** tab.\n\n![](https://files.readme.io/e7b45dc1bc95aa700297d6bfa8c4a39d80f7dceac615b15fd461c5b479d77523-image.png)\n\n> 👍\n> \n> You have successfully created an `Event` sync to Iterable!\n\n> 📘\n> \n> Experiencing any issues configuring Syncs to Iterable? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and we’ll be in touch shortly!\n\nUpdated 5 months ago\n\n* * *\n\nWant to discover more ways to combine GrowthLoop and Iterable? Click below for a full list of use cases!\n\n* [Integrate with Iterable](https://docs.growthloop.com/docs/integrate-with-iterable)","2024-03-20T21:02:35.809Z","fd23eeb8-0c6e-45bc-992a-3f310fcac732",[],[],{"_40":708,"_128":709,"_130":710,"_132":711,"_134":-5,"_13":-5,"_120":712,"_122":136,"_25":713,"_138":-5,"_139":714,"_141":715},"How to enable Marve | GrowthLoop Docs","how-to-enable-marve-growthloop-docs","https://docs.growthloop.com/docs/enable-marve","In this article, you'll learn how to enable Marve\n\nMarve unlocks several generative AI capabilities across the GrowthLoop platform that enable your teams to more easily activate audiences to marketing and sales channels.\n\nThere are a few key capabilities Marve unlocks today:\n\n* [**Marve Studio**](https://dash.readme.com/project/growthloop/v1.0/docs/marve): Your teams can use natural language to brainstorm and create audiences.\n* **Marve Descriptions:** Marve can explain your data fields to business teams right in the audience and journey builder to help them understand what filters they are using.\n* **Audience Discovery**: Marve will proactively suggest audiences to your marketers every week based on learnings from previously exported audiences.\n\nEnabling Marve only takes a few clicks. Marve must be enabled for each `Dataset Group` you would like to use it with. This ensures that you have full control over which datasets are leveraged.\n\n* From the Home Page, click on \"Datasets\" on the left-hand menu\n* Click on the \"Dataset Group\" you'd like to enable Marve for.\n* Click on the \"Marve\" tab\n* Read the [GrowthLoop Generative Marketing Acceptable Use Policy](https://www.growthloop.com/generative-marketing-acceptable-use-policy)\n* Certify that you have and accept the Acceptable Use Policy\n* Click Submit\n\nThis will enable Marve for your Dataset Group. Now users can leverage Marve Studio to build audiences and will begin receiving audience suggestions directly on GrowthLoop home every week.\n\nMarve was designed to be privacy-centric from the ground up. Marve Studio trains only on audience metadata, filters you have used in audiences, dataset names, dataset column names, and column descriptions. Marve **does not** train on individual row data within your datasets that are connected to GrowthLoop. This design is meant to make it simple for customers to ensure no PII is used in training Marve. If you have any questions about data use with Marve, please reach out to our team at [support@growthloop.com](mailto:support@growthloop.com), who will be happy to dive in further.\n\n> 📘\n> \n> Marve is available to customers on our enterprise plan. To enable Marve in your account, please contact [support@growthloop.com](mailto:support@growthloop.com).\n\nWe hope you found this helpful. If you have any questions, please don’t hesitate to reach us at [support@growthloop.com](mailto:support@growthloop.com).\n\nUpdated 5 months ago\n\n* * *\n\nNow that you have Marve enabled, take a look at how to use Marve Studio to build audiences.\n\n* [Marve](https://docs.growthloop.com/docs/marve)","2025-06-20T22:58:06.728Z","80c3e4a4-c41f-482f-8ac2-3ec6191825c6",[],[],{"_40":717,"_128":718,"_130":719,"_132":720,"_134":-5,"_13":-5,"_120":721,"_122":136,"_25":722,"_138":-5,"_139":723,"_141":724},"How to export an audience in GrowthLoop | GrowthLoop Docs","how-to-export-an-audience-in-growthloop-growthloop-docs","https://docs.growthloop.com/docs/export-an-audience","# How to export an audience in GrowthLoop\n\nLearn how to configure your exports to downstream channels for audience activation.\n\nIn this article, you’ll learn the basics for how to export an audience in the GrowthLoop application.\n\n> 📘\n> \n> If you need a refresher on how to build an audience, check out [create an audience](https://docs.growthloop.com/docs/create-an-audience).\n\nBefore exporting an audience, you’ll need to have your destination set up in GrowthLoop. Here is a library of [**destination**](https://www.growthloop.com/help-center-categories/destinations) tutorials you can review.\n\n1. Navigate to the audience you’d like to export, and select `Export` from the dropdown menu on the right hand side.\n2. The `Create Export` modal will appear, listing all of the destinations you’ve connected to your GrowthLoop application.\n3. After selecting your desired destination, you will be required to specify the `Match Fields`. This typically refers to the user identifiers (such as email, phone number, or device ID) that the destination platform uses to match and activate your audience.\n4. Once you've mapped the appropriate fields from your table to the required match fields, you’ll be asked to configure your `Export Settings`:\n 1. `Export Name`: Any name you want to assign to this export, defaults to Audience name. This name will not be passed on to destinations and is only used to differentiate exports in the GrowthLoop app.\n 2. `Campaign Type`: \"Ongoing\" or \"One Time\". \"Ongoing\" means that the audience export will be repeated on a periodic schedule.\n 3. `Frequency`: The time interval to set for Ongoing campaign types. This will overrule the default frequency sync set when you first create a destination.\n 4. `Timing fields`\n 1. `Start`: Choose whether the export should begin \"Now\" or be \"Scheduled\" for a future time.\n 1. Selecting \"Now\" will trigger the export within the next 15 minutes.\n 2. Selecting \"Schedule\" will prompt you to enter a specific Date, Time, and Timezone (see below).\n 2. `Date`, `Time`, and `Timezone`: These fields appear when \"Schedule\" is selected under Start.\n 1. `Date`: The day the export should begin.\n 2. `Time`: The specific time on the selected date when the export should start.\n 3. `Timezone`: The time zone in which the scheduled export should occur (e.g., America/Los\\_Angeles). This ensures the export triggers at the correct local time.\n 3. `End`: Set to \"Never\" or a specific end Date and Time. This option is not applicable for One-Time campaigns.\n 4. `Select days of the week`: Multi-select control for each day, starting with Sunday. By default, all days are selected. This field is not applicable for Weekly or Monthly frequencies.\n 5. `Personalization Fields`: Additional fields from your primary dataset to send to the selected destination. This option will only appear for destinations that support personalization fields, which are typically email destinations or CSV exports.\n 6. `Preview Audience with Additional, Match and Consent Fields`: Click to see a sample of your audience, including additional, match, and consent fields, to make sure everything looks right. User traits and custom attributes are not included in the export preview at this time.\n\n> 📘\n> \n> If you schedule an audience export with a daily frequency at a specific date and time (e.g., Tuesday at 6:00 AM EST), all future exports will also run at 6:00 AM EST unless changed.\n\n5. After specifying the `Export Settings` and `Match Fields`, you can click the `Export` button at the bottom.\n\n> 📘\n> \n> If you attempt to re-export to the same destination, the tile will appear grayed out (except for CSV and bucket destinations such as S3 and GCS). To proceed, you can either:\n> \n> * Update the export settings by clicking \"Manage\" on the Exports tab, then clicking the \"Run\" button. Or\n> * Create a new audience for export.\n\nAfter an audience export has been initiated, an `Exports` tab will appear in the Audience Builder UI. This tab contains a summary of all audience destinations and export runs, including details about added, removed, and rejected records. Below is a breakdown of what each column represents:\n\n* `Destination`: The platform where the audience is being sent (e.g., Iterable).\n* `Status`: Indicates whether the export is processing, successfully completed, or encountered errors.\n* `Export Time`: The timestamp when the export was initiated.\n* `Added`: The number of records added to the audience and sent to the destination.\n* `Removed`: The number of records removed from the audience because they no longer meet the criteria.\n* `Rejected`: The number of records that failed to export due to errors (e.g., formatting issues, missing data).\n* `Export ID`: A unique identifier for the export run, which can be referenced in logs or troubleshooting.\n* `Error Details`: Provides additional information if any records were rejected during export.\n\n> 📘\n> \n> * If your audience has a treatment/control split applied, only customer records randomly assigned to the Treatment group will be exported. The number of records sent for export may differ slightly from the Treatment number in the Audience Builder UI\n> * For exports to the Snowflake destination, removals will not appear in the 'Removed' column, meaning all exported records are logged as 'Added,' even if they were previously removed and re-added.\n\n‍Its possible to disable an export by un-checking the `Enabled` box on the left hand side.\n\nFor Ongoing campaigns, you can manually trigger new export runs by clicking the `Run` button on the right hand side.\n\n> 📘\n> \n> For one-time campaigns, clicking the `Run` button will **not** trigger a new export, even if a success message appears. Additionally, clicking this button will override the scheduled daily run and reset it to the default schedule after the first run.\n\nIt’s also possible to modify the export schedule by selecting `Manage` from the dropdown menu beside the `Run` button. You can modify the frequency, End date and days of the week for any Ongoing campaigns. If the Start date is set for a future date, its also possible to update this value.\n\nYou can also convert One Time campaigns into Ongoing by selecting the same ‘Manage’ option.\n\n> 📘\n> \n> It is not possible to convert Ongoing campaigns into One Time\n\nYou can export the same audience multiple times to the same destination, giving you the flexibility to test different configurations or run variations without duplicating audiences.\n\n* Export the same audience to a destination multiple times with unique configurations.\n* Each export must have a unique name to prevent conflicts. Export names will follow this pattern:`_GL_Audience_`(e.g., `High_Spenders_GL_Audience_21328`).\n* The system will show a warning if a duplicate name is used.\n* A preview is displayed to show how the export name will appear in the destination before sending.\n\n> 📘\n> \n> This functionality applies to **new export configurations** going forward.\n\nIn addition to the GrowthLoop interface, you can trigger any audience export through the GrowthLoop API.\n\nThrough the GrowthLoop API you can:\n\n1. `List all Exports`: View a list of all Exports you have setup for audiences.\n2. `Get an Export`: View a specific Export with its Export Metadata and `Export ID`\n3. `Trigger Export`: Trigger a specific Export utilizing its `Export ID`\n\nYou can view and test the GrowthLoop API in our [API Reference](https://docs.growthloop.com/reference/audiences).\n\n> 📘\n> \n> Experiencing any issues exporting Audiences? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and we’ll be in touch shortly!\n\nUpdated 9 days ago\n\n* * *","2024-03-20T21:02:26.092Z","13365f44-c880-4f2b-a5dd-ea9559922761",[],[],{"_40":726,"_128":727,"_130":728,"_132":729,"_134":-5,"_13":-5,"_120":730,"_122":136,"_25":731,"_138":-5,"_139":732,"_141":733},"How to export an audience to a CSV | GrowthLoop Docs","how-to-export-an-audience-to-a-csv-growthloop-docs","https://docs.growthloop.com/docs/csv","# How to export an audience to a CSV\n\nLearn how to export audiences to a CSV.\n\nThis article outlines the steps necessary to export an audience to CSV.\n\nTo export an audience to CSV, create an audience or select an existing audience, and click Export in the top right corner.\n\n![](https://files.readme.io/ab83974-csv1.png)\n\nSelect the CSV destination.\n\n![](https://files.readme.io/5f3a40c-csv2.png)\n\n‍Fill out the following fields, click Download CSV, and your audience will immediately start downloading to CSV in your browser!\n\n**File Name:** This will be the name of the CSV file downloaded to your computer.\n\n**Fields:** Please select the personalization fields you’d like to appear in your CSV export (e.g. NAME, ADDRESS, CITY, STATE). Select the Fields you'd like to include in your CSV from your Dataset. Each member of your audience will be exported as a single row in the CSV and include each of the Fields you select here.\n\nTo export all Fields in the Dataset for this specific audience click \"Select All\" and it will auto-populate all Fields for your export.\n\n![](https://files.readme.io/e473492-csv3.png)\n\n‍ \n‍Congratulations! You have exported your first audience to CSV.\n\nExperiencing any issues exporting audiences to CSV? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and we’ll be in touch shortly!\n\nNote: Currently CSV export is limited to audiences under 300,000 records.\n\nLooking to connect with other sales and marketing destinations for audience activation? Click Here to find more information in our Help Center!\n\nYou can find our full list of subprocessors in our DPA.\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:37.920Z","29ada9bd-eb4d-4ca1-9cf9-d91ae9409bec",[],[],{"_40":735,"_128":736,"_130":737,"_132":738,"_134":-5,"_13":-5,"_120":739,"_122":136,"_25":740,"_138":-5,"_139":741,"_141":742},"How to import popular data sources to GrowthLoop | GrowthLoop Docs","how-to-import-popular-data-sources-to-growthloop-growthloop-docs","https://docs.growthloop.com/docs/import-data-sources","# How to import popular data sources to GrowthLoop\n\n## Ingest Data Sources\n\nEmpower your organization to ingest customer data directly from popular sources (eg, Salesforce) to your Data Cloud and immediately activate them across your marketing channels.\n\n* Facebook ads\n* Google Ads\n* The TradeDesk\n\n \n\n* Salesforce CRM\n* Dynamics CRM\n\n \n\n* Pardot\n* Salesforce Marketing Cloud\n* Sailthru\n* Braze\n* Iterable\n\nEasy Button empowers organizations to ingest data from popular sources directly into your Data Cloud and immediately activate it across all channels. It sets up a data sync from source to GrowthLoop, instantiates data models to make the raw source data usable, and connects the desired datasets to the GrowthLoop app for immediate use in building and exporting audiences.\n\n**Estimated time to set up:<15 minutes**\n\nEasy Button supports ingestion and modeling of Salesforce CRM data.\n\nGrowthLoop can support any of the 300+ sources found here: [https://www.fivetran.com/connectors](https://www.fivetran.com/connectors)\n\nTo request a new source, please reach out to [support@growthloop.com](mailto:support@growthloop.com).\n\nEasyButton allows you to start ingesting data with a click of a few buttons. Let's walk through setting up a new organization and then using Easy Button to ingest Salesforce data.\n\nAfter connecting your data warehouse, use the lefthand menu to select ‘Sources’ from the ‘Data Configuration’ option:\n\n![](https://files.readme.io/06220f5-onboarding.png)\n\nOnce you are in the organization after onboarding we are ready to setup our sources.\n\n![](https://files.readme.io/e6c0d4b73ea6d19bb7bb5ce691890d1b15947fb1a34973223b6dd0e3aed01b1d-Screenshot_2024-08-29_at_8.33.47_AM.png)\n\n![](https://files.readme.io/3d330dfb2105ac2ff497964825c02e6606013fd359ee32c90c17429b461183d5-Screenshot_2024-08-29_at_8.35.23_AM.png)\n\n![](https://files.readme.io/837e32b-salesforce_source.png)\n\nYou will be redirected to Fivetran.\n\n![](https://files.readme.io/730b170-fivetran_auth.png)\n\nRefer to the Setup Guide provided by Fivetran for more info.\n\n![](https://files.readme.io/2c7426d-fivetran_authorize.png)\n\nYou will be redirected to a Salesforce login modal.\n\n![](https://files.readme.io/b6a70cb-sources_salesforce_login.png)\n\nYou will be returned to Fivetran.\n\n![](https://files.readme.io/8daf8c9-sf_test.jpg)\n\nIf you do not see “Authentication Succeeded”, then likely there was an error with your credentials. Try again, and if that doesn’t work, submit a support ticket.\n\nYou will be returned to GrowthLoop.\n\n![](https://files.readme.io/f5e121d-sources_configuration.png)\n\n![](https://files.readme.io/55acb15-sources_list.png)\n\nOnce you see the status as “Active”, this indicates the raw data has been synced to your data warehouse\n\nThe raw dataset will be called `raw_salesforce_import_{x}` where x is the number of the source that has been set up. In this case, since it was the latest source set up, it is `raw_salesforce_import_6`.\n\n![](https://files.readme.io/6956a15-sources_dataset_setup.png)\n\nFor more information or to provide feedback to the team, please reach out to [support@growthloop.com](mailto:support@growthloop.com) We can’t wait to hear from you!\n\nUpdated 5 months ago\n\n* * *\n\n* [Setup Datasets](https://docs.growthloop.com/docs/setup-datasets)\n* [Setup Dataset Groups](https://docs.growthloop.com/docs/setup-dataset-group)","2024-03-20T21:02:22.484Z","31826374-9e87-4f84-b839-4eb2cbd9091d",[],[],{"_40":744,"_128":745,"_130":746,"_132":747,"_134":-5,"_13":-5,"_120":748,"_122":136,"_25":749,"_138":-5,"_139":750,"_141":751},"How to invite and manage teammates in GrowthLoop","how-to-invite-and-manage-teammates-in-growthloop","https://docs.growthloop.com/docs/invite-and-manage-teammates","## Invite and Manage Team Members\n\nIn this help doc, we’ll walk you through the steps for inviting your teammates to GrowthLoop, adding them to the right teams and managing their roles and access.\n\nThe first step to have your teammates join GrowthLoop is to invite them. To do that, head over to the **Organization** menu on the left hand side and click on the **Invitations** tab.\n\nThere you’ll see an **Invite Teammates** button which opens the following modal. If you (who is sending the invite) only belong to 1 team, the new user will automatically be invited to the same team and the modal does **not** ask you to pick a team to invite your teammate to.\n\n![](https://files.readme.io/12cadc0-Untitled.png)\n\nIf you belong to multiple teams, then the invitation modal prompts you to **choose the team** you’d like to invite the new user to, like the screen below:\n\n![](https://files.readme.io/21a29dc-Untitled_1.png)\n\nEnter your teammate’s email address, define their role and include a quick invitation message before you press **Send invitations**.\n\nYour teammate will then receive an email from [Solutions@GrowthLoop.com](mailto:Solutions@GrowthLoop.com) that looks something like this:\n\n![](https://files.readme.io/81ffcaa-Untitled_2.png)\n\nOnce they click the link in the email to join your organization, they’re prompted to sign up, either using Google OAuth or by setting up an email & password. **Make sure they pick the Sign Up tab.**\n\n![](https://files.readme.io/5f8394d-Untitled_3.png)\n\nOnce they join, they’re added to the team you invited them to.\n\nTo add a teammate to a different team in your organization, head over to the **Organization** menu on the left hand side and click on the **Teams** tab.\n\nYou can create new teams using the **Create Team** button on the top-right side of the page and define **Source Connections** that they have access to as well as existing users you want to add to them by default.\n\nHowever if you’re adding a newly joined teammate to an existing team, click the “**Add User to ``”** button, which launches the following modal:\n\n![](https://files.readme.io/5f23bb4-Untitled_4.png)\n\nPick one or more teammates and click the **Add Users** button. And now the users are added to that team.\n\nIf you would like to remove a user from a team, you’ll see a **Remove** button next to their email for every team they’re part of.\n\nOnce in a while you’ll need to change a teammate’s **role** or remove their access from GrowthLoop. To do that, you can head over to the **Organization** menu and click the **Users** tab.\n\nEvery user has their role defined and you can simply choose the appropriate role for them from the drop-down. However, refer to our docs on [privileges per role](https://docs.growthloop.com/docs/role-management) to make sure you assign the appropriate role to your teammates.\n\nAnd if you need to deactivate a teammate’s access to GrowthLoop turn off the **Activate** toggle in front of their name, which prevents them from logging into the platform if deactivated. You can always reactivate the user and they can log back in.\n\n![](https://files.readme.io/d2da584-Untitled_5.png)\n\nWe hope you find this resource helpful and if you have any questions, please contact our team at [support@growthloop.com](mailto:support@growthloop.com).\n\nUpdated 5 months ago\n\n* * *","2025-06-20T22:58:07.842Z","2bc7fa29-ad58-44da-b542-e05316f91bde",[],[],{"_40":753,"_128":754,"_130":755,"_132":756,"_134":-5,"_13":-5,"_120":757,"_122":136,"_25":758,"_138":-5,"_139":759,"_141":760},"How to manage PII within your datasets | GrowthLoop Docs","how-to-manage-pii-within-your-datasets-growthloop-docs","https://docs.growthloop.com/docs/pii-management","# How to manage PII within your datasets\n\n## PII Management\n\nLearn how to manage PII permissions and usage across the GrowthLoop platform\n\nHere at GrowthLoop, we understand that data privacy comes first. That’s why we’ve introduced Personally Identifiable Information (PII) tagging to ensure that your business teams can make the most of your customer data while never compromising on privacy or security.\n\nGrowthLoop protects PII in a few ways. First and foremost, the GrowthLoop Audience Builder queries your customer data in place, so it never leaves the safety\n\nPII is information that can be used, alone or in combination with other data, to identify a specific individual. Common examples of PII include first name, last name, and social security number.\n\nWhen you tag columns from your underlying datasets as **PII fields**, GrowthLoop blocks them from appearing as filters in your Audience Builder. Tagging columns as PII also prevents users from downloading any CSVs with this data.\n\nIndividuals in your organization with the “Owner” or “Admin” role within their GrowthLoop app can tag PII fields.\n\nYou can tag customer data as PII when connecting a new dataset, or editing an existing dataset connection.\n\n1. From the GrowthLoop homepage, click **Datasets** on the left side of the screen.\n2. Click **New Dataset**\n3. Once you have identified the dataset to connect and provided it a name within the GrowthLoop app, scroll to the table of fields below. You can identify a field as PII by checking the box in the **PII** column of the field’s row. Note that if you identify a field as PII, you will no longer be able to set that field as default because it cannot be shown in the Audience Builder.\n4. Once you have finished configuring your dataset, click **Save**. You’re good to go!\n\n1. From the GrowthLoop homepage, click **Datasets** on the left side of the screen.\n2. Scroll to the table of datasets at the bottom of the screen and find the dataset you wish to edit.\n3. Within the modal, scroll down to the table of fields. You can identify a field as PII by checking the box in the **PII** column of the field’s row. Note that if you identify a field as PII, you will no longer be able to set that field as default because it cannot be shown in the Audience Builder.\n4. Once you have finished configuring your dataset, click **Save** You’re all set!\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:23.993Z","e39a414f-37c5-4a55-a9c7-81fd8fe2c52c",[],[],{"_40":762,"_128":763,"_130":764,"_132":765,"_134":-5,"_13":-5,"_120":766,"_122":136,"_25":767,"_138":-5,"_139":768,"_141":769},"How to modify journeys | GrowthLoop Docs","how-to-modify-journeys-growthloop-docs","https://docs.growthloop.com/docs/modify-a-journey","## Modify a Journey\n\nIn this article, you'll learn how to modify journeys before and after publish\n\nAs you build out marketing and sales journey sequences with your team members it can be an iterative process. This means you'll frequently be modifying your journeys both prior to publishing and after publishing them.\n\n \n\n* From the Home Screen, click on \"Journeys\" in the left-hand menu.\n* You will now see a list of your journeys\n* Click on a journey in `Draft` status you would like to modify to be taken to the journey canvas.\n* Since the journey is in `Draft` status and has not been published:\n * You are able to modify:\n * Settings\n * Start time\n * End time\n * Frequency\n * Re-Entry\n * Global Exit Node\n * Entry Audience\n * Note: You can only select audiences from the same dataset group.\n * Criteria Nodes\n * Variation Nodes\n * Destination Nodes\n * Delay Nodes\n * You are able to add or delete:\n * Any node type to canvas\n* Once you have modified your journey, you can click \"Save\" on the right side of the journey title bar.\n\nOften times customers will start by publishing a journey and having it run through one time for members of an audience and then analyze the results. If the journey is successful, you can make this journey an always-on program easily within GrowthLoop.\n\n* From the Home Screen, click on \"Journeys\" in the left-hand menu.\n* You will now see a list of your journeys\n* Click on a \"One Time\" journey in `Published` status you would like to make an \"Always On\" journey\n* Click on the \"Settings\" tab in the journey top menu\n* Click the \"Journey Schedule\" dropdown in the \"Journey Settings\" card.\n* Select \"Always On\". This will turn your journey into an ongoing journey so new qualifying users can continuously enter the program.\n* Click \"Save\" on the right side of the journey title bar.\n* Click \"Confirm\" in the publish confirmation notice.\n\nOnce a journey has been published, you may change your mind on whether you want users to be able to re-enter the journey in the future. To accomplish this, you can modify your Re-Entry criteria.\n\n* From the Home Screen, click on \"Journeys\" in the left-hand menu.\n* You will now see a list of your journeys\n* Click on any journey with `Published` status.\n* Click on the \"Settings\" tab in the journey top menu\n* Navigate to \"Additional Settings\" card\n* Under \"Can users re-enter journey?\", click \"No\".\n* Click \"Save\" on the right side of the journey title bar.\n* Click \"Confirm\" in the publish confirmation notice.\n* Users who have completed the journey will no longer be allowed to re-enter this published journey even if they qualify to do so according to the entry criteria.\n\nOnce a journey has been published, you may decide you want users to be able to re-enter the journey again after a certain period of time. To accomplish this, you can modify your Re-Entry criteria.\n\n* From the Home Screen, click on \"Journeys\" in the left-hand menu.\n* You will now see a list of your journeys\n* Click on any journey with `Published` status.\n* Click on the \"Settings\" tab in the journey top menu\n* Navigate to \"Additional Settings\" card\n* Under \"Can users re-enter journey?\" click \"Yes.\"\n* Specify the \"Re-Entry Delay\" required.\n * This is the time a user must wait from when the user exited the journey to when they are allowed to re-enter the journey again.\n * Select days, hours, weeks, and minutes from the dropdown.\n * Insert the amount of time as an integer you would like to ensure users wait to re-enter the journey.\n * **Note:** If a user qualifies to re-enter the journey and your \"Re-Entry Delay\" has not been met, they will not enter the journey. The user must wait until they qualify to enter the journey and the \"Re-Entry Delay\" is satisfied.\n* Click \"Save\" on the right side of the journey title bar.\n* Click \"Confirm\" in the publish confirmation notice.\n* Users who have completed the journey will now be able to re-enter the journey again.\n\nIn certain cases, you may want to modify your journey after it has been published. Typically, it is a best practice to copy your journey, make the changes, and publish the new journey. However, sometimes you just need to modify the current journey you have in place.\n\n* From the Home Screen, click on \"Journeys\" in the left-hand menu.\n* You will now see a list of your journeys\n* Click on a journey in `Published` status you would like to modify to be taken to the journey canvas.\n* Since the journey has been published, you can modify it with a certain set of interactions.\n * Settings\n * Start time: You can modify the start time if it has not already passed.\n * End time: You can extend the end time of the journey.\n * Frequency: You can change journeys from \"one time\" to \"always on\" or \"recurring scheduled\"\n * Re-Entry: You can modify if a journey allows re-entry or not. And the time a user must wait to re-enter a journey.\n * Criteria Nodes: To modify a criteria node:\n * Click the ellipsis (...) on the right-hand side of the node.\n * Click \"Settings.\"\n * Modify criteria in the canvas.\n * Click \"Save\" on the right side of the journey title bar.\n * Click \"Confirm\" in the publish confirmation notice.\n * Delay Nodes\n * Click the ellipsis (...) on the right-hand side of the node.\n * Click \"Settings.\"\n * Modify any settings of the delay node.\n * Click \"Save\" on the right side of the journey title bar.\n * Click \"Confirm\" in the publish confirmation notice.\n * Destination Nodes: Destination nodes are not currently modifiable for published journeys. If you would like to change a destination, you can copy your journey, change any destination node, and re-publish.\n\n> 📘\n> \n> It is important to note, that any journeys modified after publish will be re-published. This means that if specific nodes are modified will be applied to new users that enter the journey and users currently in the journey that have not reached that node yet.\n\nHave any questions about modifying your journeys? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com).\n\nUpdated 4 months ago\n\n* * *","2025-06-20T22:58:20.075Z","3fce933e-cc8d-4e78-8625-7eacc2a0e368",[],[],{"_40":771,"_128":772,"_130":773,"_132":774,"_134":-5,"_13":-5,"_120":775,"_122":136,"_25":776,"_138":-5,"_139":777,"_141":778},"How to monitor Journeys | GrowthLoop Docs","how-to-monitor-journeys-growthloop-docs","https://docs.growthloop.com/docs/journey-monitoring","## Monitor a Journey\n\nLearn how to monitor your journeys after they are published\n\nIn this article, you'll learn how to monitor how your users are flowing through your journeys once they are published.\n\nThere are a few ways to see how users are running through your journey:\n\n1. **Live Viewer:** This gives you a live understanding of where users are in your journey.\n2. **Activity Tracker**: Allows you to see every step that is processed in your journey and if any errors occurred while that step was processing. This is great for debugging and gives you full visibility into every process that runs in your journey as users advance through.\n3. **In your Data Cloud:** See every user in each node of your journey by querying your data cloud.\n\nTo view where users are sitting in your journey at a glance you can use **Journey Live Viewer**.\n\n1. Click on **Journeys** in the left-hand menu.\n \n2. Select your **Published** Journey\n \n3. On each journey step you can see:\n \n 1. **In Process**: Number of users that are currently in journey step.\n 2. **Completed**: Number of users that have completed step.\n4. On each journey step you can see:\n \n 1. **In Process**: Number of users that are currently in journey step.\n \n ![](https://files.readme.io/da03700-Live_Viewer.png) \n \n 2. **Completed**: Number of users that have completed step.\n \n ![](https://files.readme.io/5e09fa6-Live_Viewer_-_In_progress.png)\n\n \n\n5. Here is what it looks like on **Canvas**:\n\n![](https://files.readme.io/37ae397-Live_Viewer_-_Completed.png)\n\nThe **Journey Activity Tracker** helps you dive deeper and understand when, how, and the result of every step that is processed in your journey. This is the fastest way to debug your journeys and ensure they are operating exactly as you expect.\n\n1. Click on **Journeys** in the left-hand menu.\n \n2. Select your **Published** Journey.\n \n3. Select **Activity** tab in the journey sub-menu.\n \n4. In the **Activity Tracker** you can see every step, when it was processed, and the result.\n \n 1. **Step ID:** This is the Unique Identifier for the Journey Step that was processed.\n \n 2. **Step Name:** This name of the step (the name you provided) on Journey Canvas.\n \n 3. **Step Type:** This is the type of step: Entry, Criteria, Destinations, Experiments, and Delay.\n \n 4. **Completed** This shows the result of processing the step.\n \n 1. **Criteria Step** : Show how many users went down the **Yes** path and **No** path.\n \n 2. **Delay Step**: Show how many users completed the delay and advanced to the next node.\n \n 3. **Destination**: Show how many users were processed and sent to destination.\n \n 4. **Experiments**: Show how many users were allocated and advanced in that experiment variation.\n \n 5. **Globally Exited**: Show how many users were exited from your journey while this step was processed because they met your **global exit criteria**.\n \n 6. **Status**\n \n 1. **Processed**: This shows you that the journey node was successfuly processed.\n 2. **Error**: This shows you that the node had an error while processing. You can click the **Error** to view more details and gain an understanding of what caused the users to not be successfully processed at that journey step.\n 7. **Process Time**: Shows you when the journey step was processed.\n \n\n![](https://files.readme.io/a60ae69-Activity_Tracker.png)\n\nFor analytics and technical users, the best part of using GrowthLoop on your data cloud is you can run a simple SQL query and see where every user is within a journey right within your data cloud.\n\nGrowthLoop stores **journey state** tables directly in your data cloud, so you can:\n\n1. See what users are in a particular step of your journey **right now**\n2. See what users are in a particular step of your journey on **any date in the past**\n3. See how many users are in more than 1 active journey today.\n4. See how many users have never been in a journey.\n\nReview our [Journey Data Cloud Storage documentation](https://docs.growthloop.com/docs/journey-state-tables) to get started.\n\nUpdated 5 months ago\n\n* * *\n\n* [Data Cloud Storage](https://docs.growthloop.com/docs/journey-state-tables)","2025-06-20T22:58:21.120Z","6ce84cc9-08a2-4e47-8a26-5b905e0b65c9",[],[],{"_40":780,"_128":781,"_130":-5,"_132":782,"_134":-5,"_13":-5,"_120":783,"_122":784,"_25":785,"_138":-5,"_139":786,"_141":787},"How to Refresh a Dataset in GrowthLoop","how-to-refresh-a-dataset-in-growthloop","To refresh a dataset in GrowthLoop and ensure that new fields, such as 'deal_type', are visible, follow these steps:\n\n1. Navigate to the Source Connection tab in the Organization Management Panel.\n2. Locate the 'Last Schema Refresh' column to check the last refresh time.\n3. Click the 'Refresh' icon to update the schema immediately.\n\nThis process updates all field and table changes for your Source Connection, making new fields and tables available for use in audience and journey building. Please note that the refresh process can take up to 15 minutes to complete.","2024-12-10T21:36:44.286Z","2024-12-30T16:00:29.641Z","88fb3b45-9b75-4e95-b7eb-2451239a3f14",[],[],{"_40":789,"_128":790,"_130":791,"_132":792,"_134":-5,"_13":-5,"_120":793,"_122":136,"_25":794,"_138":-5,"_139":795,"_141":796},"How to set up Amazon S3 as a destination | GrowthLoop Docs","how-to-set-up-amazon-s3-as-a-destination-growthloop-docs","https://docs.growthloop.com/docs/amazon-s3","# How to set up Amazon S3 as a destination\n\nLearn how to set up Amazon S3 as a destination so you can start exporting audiences to it.\n\nIn this Help Center article, we will walk you through the steps to get Amazon S3 connected as a destination in the GrowthLoop web application. Once connected, you will be able to send your audience segments to an S3 bucket as CSVs!\n\n1. Ensure you have an S3 bucket created for GrowthLoop to land audience exports.\n \n2. Ensure you have created an IAM user, and attached a policy that provides access to the S3 bucket in step #1. The user will need the following permissions on the s3 bucket:\n \n ```\n {\n \"Version\": \"2012-10-17\",\n \"Statement\": [\n {\n \"Sid\": \"VisualEditor0\",\n \"Effect\": \"Allow\",\n \"Action\": [\n \"s3:GetObjectVersionTagging\",\n \"s3:GetObjectAcl\",\n \"s3:GetObjectVersionAcl\",\n \"s3:DeleteObject\",\n \"s3:GetObjectAttributes\",\n \"s3:PutObject\",\n \"s3:GetObject\",\n \"s3:PutEncryptionConfiguration\",\n \"s3:GetEncryptionConfiguration\",\n \"s3:GetObjectTagging\",\n \"s3:GetObjectVersion\",\n \t\t\t\t\t\t\t\t\"s3:GetBucketACL\"\n ],\n \"Resource\": [\n \"arn:aws:s3:::test-export-from-fw\",\n \"arn:aws:s3:::test-export-from-fw/*\"\n ]\n }\n ]\n }\n ```\n \n3. Ensure the IAM user mentioned in step #2 has a programmatic access key assigned. The Access Key and Secret Access Key will be used in GrowthLoop to connect to the s3 bucket\n \n\n1. Click **Destinations** in the left rail\n\n![](https://files.readme.io/a02a4ea-Add_destination.png)\n\n1. Click **New Destination** on the top right corner of then **Add S3**\n\n![](https://files.readme.io/1d5d3cc-select_s3.png)\n\n2. Fill out the following destination info\n\n![](https://files.readme.io/0234e10-s3_destination_config.png)\n\n* **Destination Name:** This how the destination will be named and referred to in to the app going forward\n* **Sync Frequency:** Please select Daily or Hourly, this will control how often GrowthLoop exports audiences to S3\n* **Bucket:** Please enter the bucket name as shown in the AWS S3 console\n* **AWS Access Key:** Please past in the contents of the Access Key generated for your IAM user in step #3 of the prerequisites\n* **AWS Access Secret:** Please paste in the contents of the Secret Access Key generated in step #3 of the prerequisites\n* **Columns to Export:** Please provide a comma separated list of columns you’d like to appear in your csv export (e.g _NAME,ADDRESS,CITY,STATE_)\n\nClick Create. You now have connected Amazon S3 as a destination.\n\nTo export an audience to Amazon S3:\n\n1. Select an audience and click **Export**\n \n2. Click **Activate**, and choose your unique identifier for your customer\n \n\n![](https://files.readme.io/edb99fa-activate_s3.png)\n\n3. Fill out the following fields, click **Start Export** and your audience will immediately start exporting to S3!\n\n![](https://files.readme.io/5937907-start_export_s3.png)\n\n* **Name:** This is the name of your audience that will be passed through to the filename in S3\n* **Export Type:** Please select either Export All Records or Export Updates (Deltas). Export All Records will export a full audience list on each export, and Export Updates (Deltas) will start with a full audience list export but will export only updates to the original audience list with each subsequent export\n* **Personalization Fields:** Please select the personalization fields you’d like to appear in your csv export (e.g _NAME,ADDRESS,CITY,STATE)_\n\nCongrats! You have exported your first audience to AWS S3!\n\nExperiencing any issues connecting to Amazon S3 as a destination? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and we’ll be in touch shortly!\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:36.609Z","57f3b16a-fa4c-456e-b18f-99dc717e05a8",[],[],{"_40":798,"_128":799,"_130":800,"_132":801,"_134":-5,"_13":-5,"_120":802,"_122":136,"_25":803,"_138":-5,"_139":804,"_141":805},"How to set up an experimental audience | GrowthLoop Docs","how-to-set-up-an-experimental-audience-growthloop-docs","https://docs.growthloop.com/docs/experiments","# How to set up an experimental audience\n\nIn this article, we will walk through the steps to set up a treatment/control split for an experimental audience. If you are curious what this treatment/control split does, how to pick the appropriate split sizing, or tips for maximizing your chances of achieving statistical significance in your campaign evaluation, we highly encourage you to check out our [GrowthLoop Campaign Evaluation Methodology Explained](https://docs.growthloop.com/docs/experiments) article.\n\n‍\n\nCreating your experimental audience is easy with GrowthLoop Audience Builder! Simply apply the Flex Filters necessary to narrow down your customer segment to just those fitting the desired criteria. Step-by-step instructions for how to do this can be found [here](https://docs.growthloop.com/docs/create-an-audience) if needed.\n\n![](https://files.readme.io/c566bc7-Screenshot_2024-01-23_at_2.00.42_PM.png)\n\nBefore you save your audience, take a look at the **Audience Report** on the right hand side of the screen. Here you can see a live view of how many customers fit the criteria defined by the selected Flex Filters. You can also move the slider to adjust how many customers fall within the treatment group (who receive the marketing or sales intervention), and those who fall within the control group (who do NOT receive the intervention for this specific campaign). The default split shown is not necessarily a suggestion, but rather the default split established in the settings of your Audience Builder dataset, and can be changed at any time.\n\n![](https://files.readme.io/76c6c65-Screenshot_2024-01-23_at_1.51.01_PM.png)\n\n**There are several trade-offs to keep in mind when selecting the Treatment / Control Split percentage:**\n\nThere is often the temptation to bias the sample towards the treatment group in order to maximize the number of users receiving the marketing or sales intervention. Generally speaking, however, the best experimental comparisons between treatment and control groups will be achieved when the size of the groups is similar.\n\nThat said, the overall size of the audience matters a great deal when using statistical significance testing to evaluate the effectiveness of a campaign. Larger treatment group splits can be warranted if the overall size of the audience is suitably large.\n\nWhen in doubt, GrowthLoop can perform what is called a Statistical Power Analysis - an analysis used to determine the minimum sample sizes and effect size (% incremental benefit in the treatment group) required to achieve statistical significance in an experiment.\n\n**Common Approaches to Treatment/Control Split:**\n\nWhen evaluating \"evergreen\" campaigns - campaigns that will be active on an ongoing basis and apply to any new users who qualify - many marketers will opt to split their campaign into two distinct phases.\n\nIn the first phase (the assessment phase), a robust control group will be used to ensure a proper determination of the campaign's effectiveness can be achieved.\n\nIn the second phase, assuming the assessment phase resulted in a sufficiently impactful incremental performance boost, the size of the control group will be reduced to ~20% (depending on audience size) to maximize the impact of the campaign while still retaining the ability to track the campaign's performance directionally.\n\n‍\n\nOnce you are happy with the treatment/control split, all that is left to do is to save your audience and begin exporting it to your desired marketing or sales destinations! Campaign Evaluation will kick off automatically and will analyze the behavior patterns of those customers who fall in the treatment group and compare to those in the control group.\n\n* * *\n\nGrowthLoop's in-app campaign evaluation tools are a powerful way to analyze the impact of your campaigns on a wide array of business values and outcomes, all in near real-time.\n\nOur Campaign Evaluation is based on a treatment/control experimental framework, otherwise known as frequentist A/B testing - an approach that quantifies the incremental improvements in business outcomes driven by your campaigns and supports them with robust statistical significance testing.\n\nThis guide is intended to explain and inform the various decisions that must be made when designing an experiment and to detail how GrowthLoop's evaluation methodology functions, both from a general and technical perspective.\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd84a96d81c9c4_Untitled%20(13).png](https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd84a96d81c9c4_Untitled%20(13).png)\n\n_Snapshot View: Campaign Evaluation in-app for an experimental audience_\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd8470e081c9c5_Untitled%20(14).png](https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd8470e081c9c5_Untitled%20(14).png)\n\n_Snapshot View: Revenue Uplift generated when comparing treatment vs. adjusted control audience segments_\n\n‍\n\nCampaign evaluation begins during audience creation when the treatment/control split is set.\n\nThe Treatment / Control experimental design relies on using 2 (or more) experimental groups that are drawn from the same population (meaning the qualification criteria for both groups are the same).\n\nThe treatment group receives the marketing or sales intervention, while the control group does not. Because these two groups are drawn from the same population, the only difference between them is the intervention itself. Their behavior can then be compared to isolate the incremental impact of the intervention on any number of business metrics, such as revenue generated, app logins, email opens, etc.\n\n![](https://files.readme.io/ca20a86-Screenshot_2024-01-23_at_1.51.01_PM.png)\n\n_Toggling the treatment/control split within the GrowthLoop Audience Builder is simple - just move the slider!_\n\n**There are several trade-offs to keep in mind when selecting the Treatment / Control Split percentage:**\n\nThere is often the temptation to bias the sample towards the treatment group in order to maximize the number of users receiving the marketing or sales intervention. Generally speaking, however, the best experimental comparisons between treatment and control groups will be achieved when the size of the groups is similar.\n\nThat said, the overall size of the audience matters a great deal when using statistical significance testing to evaluate the effectiveness of a campaign. Larger treatment group splits can be warranted if the overall size of the audience is suitably large.\n\nWhen in doubt, GrowthLoop can perform what is called a Statistical Power Analysis - an analysis used to determine the minimum sample sizes and effect size (% incremental benefit in the treatment group) required to achieve statistical significance in an experiment.\n\n**Common Approaches to Treatment/Control Split:**\n\nWhen evaluating \"evergreen\" campaigns - campaigns that will be active on an ongoing basis and apply to any new users who qualify - many marketers will opt to split their campaign into two distinct phases.\n\nIn the first phase (the assessment phase), a robust control group will be used to ensure a proper determination of the campaign's effectiveness can be achieved.\n\nIn the second phase, assuming the assessment phase resulted in a sufficiently impactful incremental performance boost, the size of the control group will be reduced to ~20% (depending on audience size) to maximize the impact of the campaign while still retaining the ability to track the campaign's performance directionally.\n\n‍\n\nThe most common approach to splitting users into Treatment and Control groups is **Random Assignment**. In this methodology, users in the audience are assigned randomly to either the treatment or control group based on the treatment/control split selected during audience creation. By randomly assigning users between treatment and control, we avoid introducing any bias outside of the experimental intervention itself. The end result of this assignment is two experimental groups that match the specified sizing percentages.\n\n**A few technical notes on GrowthLoop's implementation:**\n\nIn the case of ongoing campaigns, when new users are added to the audience, the same random assignment approach is implemented on the entire group of newly qualifying users regardless of whether the current 'active' size of the treatment and control groups matches the split percentage. Functionally, this means that over time the cumulative treatment/control split percentage will match the specifications, but at any given time after the audience's creation, because users may drop from the treatment/control groups at different rates, the 'active' size counts may diverge slightly from the expected ratio.\n\n**Considerations:**\n\n1. While Random Assignment is a widely-used and well-understood methodology for group assignment in this experimental framework, it does have several drawbacks in the context of marketing campaign evaluation. Random Assignment works best in controlled experimental settings where all outside influences are mitigated. Marketers will often have several campaigns ongoing at any given time, however, and the audiences for these campaigns may overlap. This leads to situations in which a given user may appear in multiple treatment groups or the treatment group for one audience and the control group for another audience - introducing noise into the experiment.\n\n* Because users are randomly assigned between treatment/control in all of the affected campaigns, the experiments remain statistically independent, and as such these overlaps do not invalidate the random assignment approach. However, they do make it more challenging to establish statistically significant incremental effects, due to the performance of the control group being inflated by users who are also in the treatment group for other campaigns.\n\n2. Users retain their control/treatment label over the entire duration of their membership in a given audience, meaning that if a user exits and then re-enters a given audience, they will be assigned the same label.\n\n‍\n\nIn order to contend with the audience overlap issue discussed above, some organizations opt for the use of a **Global Control Group** in lieu of Random Assignment.\n\nThe Global Control methodology functions by randomly reserving a modest percentage of the overall marketable user base, generally somewhere in the neighborhood of 10-20%, and withholding **all** marketing from these users. As new users are acquired, the same methodology is used to add a percentage of new users to the global control based on the predetermined split.\n\nAudience definition happens the same way, but instead of randomly assigning all qualifying audience members based on some predetermined split, the control group for any given audience consists of the overlap between the qualifying audience and the global control group.\n\nFunctionally, this means that no user ever ends up in both a treatment and control group simultaneously - the global control represents a true baseline when evaluating the effect of marketing compared to no marketing at all. We, therefore, would expect less noisy measurement of incremental performance improvements.\n\nHowever, because the global control group is randomly assigned and generally only ~10-20% of the total population, we would also expect the size of the control group for any given audience to closely match the overall split. Depending on the overall size of the audience in question, this can lead to situations in which the control group is too small to achieve reliable, statistically significant comparisons with the treatment group.\n\n‍\n\nSome questions to consider when selecting a treatment/control split are...\n\n* How saturated is your marketing environment? How possible is it that a given user will qualify for two marketing campaigns simultaneously? The development of a distinct lifecycle segmentation can help greatly in mitigating the risk of multiple marketing efforts conflicting with one another.\n* How large is your overall customer base? How large are the individual audiences that you generally target?\n* What effect size/incremental performance boost do you generally expect from your marketing campaigns?\n\nBoth approaches have their advantages and disadvantages, along with strategies that can be used to mitigate their shortcomings. We are always happy to engage in a conversation about which approach best suits the needs of your business.\n\n‍\n\nOnce the audience is defined, audience members are split into treatment and control groups, and the treatment group has started receiving marketing or sales intervention, we can start the evaluation.\n\nBecause GrowthLoop's campaign evaluation platform sits directly on top of your data warehouse, we can compare the performance of the treatment and control groups across any event we can tie to the customer level. We call these **Metrics**, and they come in two different flavors: Aggregations and Conversions.\n\nAs the name suggests, **Aggregations** involve aggregating events (or the values associated with those events) over time. Aggregations first happen at the user level (e.g. how much has each user spent since joining the campaign), and are then aggregated again up to the audience level (e.g. how much have all users in the treatment group spent so far during the campaign). We can either count the number of times some event happened, or sum up all the values associated with events that took place (like the amounts associated with transactions).\n\nSome examples of Aggregation Metrics:\n\n* Total spend in the treatment group vs. control group during the duration of the campaign\n* Total number of transactions in the treatment group vs. a control group that took place within 60 days of the user being added to the campaign\n* Total number of logins in the treatment group vs. control group during the duration of the campaign\n\nAt the customer level, **Conversions** capture whether an event happened or not. The only possible values for a conversion metric are True or False. At the audience level, conversions represent the number or percent of users in the group that converted.\n\nSome examples of Conversion Metrics:\n\n* Number/Percent of users who made at least one transaction during the campaign in the treatment group vs. control group\n* Number/Percent of users who purchased a specific product/service during the campaign in the treatment group vs. control group\n\n‍\n\nAs discussed in the 'Selecting Treatment / Control Split' section above, it is often the case that the Treatment and Control groups are different sizes. When this is the case we need to normalize our metrics by group size in order to reach an 'apples-to-apples' comparison.\n\nFor example, if we have 80 users in the treatment group, 20 in the control group, and everyone spends $10, it's clearly wrong to assume that the $800 total spend in the treatment group outperformed the control group with $200 total spend. If we normalize the spend by the group size, we get $10 spend per user in both treatment in control. In other words, there's no difference in performance.\n\nIn order to arrive at the adjusted control version of a metric, we first normalize the control metric by group size, and then multiply it by the size of the treatment group. This allows for an apples-to-apples comparison between the two groups, framed in terms of the actual incremental benefit of the treatment.\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd84e34a81c9c1_Screen%20Shot%202021-10-27%20at%206.33.40%20PM.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd84e34a81c9c1_Screen%20Shot%202021-10-27%20at%206.33.40%20PM.png)\n\nThe full calculation for the example above is as follows:\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd84474681c9c3_Screen%20Shot%202021-10-27%20at%206.34.42%20PM.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd84474681c9c3_Screen%20Shot%202021-10-27%20at%206.34.42%20PM.png)\n\nThe AdjustedControl metric = $800, which is the same as Treatment meaning there was no incremental benefit to this campaign.\n\nLet's now consider the same example but where the Total Revenue metric for the Treatment group is instead $1000. In this case, when we compare the Total Revenue of Treatment to Total Revenue of AdjustedControl we get an incremental benefit (lift) of $200 for this campaign.\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd84d47981c9c6_Screen%20Shot%202021-10-27%20at%206.35.46%20PM.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd84d47981c9c6_Screen%20Shot%202021-10-27%20at%206.35.46%20PM.png)\n\nIn other words, if we had not run the campaign, we would have expected the users in the treatment group to spend a total of $800, resulting in a total of $1000 for the audience as a whole. Instead, we registered $1200 in spend, meaning the campaign generated an incremental benefit of $200.\n\nA few considerations to keep in mind when working with Adjusted Control metrics:\n\n1. Percentages are already normalized by population size, so an additional adjustment isn't necessary.\n \n2. If the size of the control group relative to the test group is very small, outliers in the control group can have an outsized impact on the adjustment metric due to being multiplied by the size of the treatment group. This is only relevant to aggregation metrics, and it's possible to include outlier adjustment on a per metric basis to account for this.\n \n\nNow that we understand how Lift is calculated, let's take a closer look at Statistical Significance Testing - The methodology that is used to determine whether an observed difference between the performance of treatment and control groups is real vs. due to random chance.\n\n‍\n\nEvaluating campaign success based on performance metrics on their own is helpful in understanding how a campaign is tracking directionally over time, but when it comes time to make an important decision about whether a given campaign should be expanded or whether it should be scrapped, how does one determine what level of performance is good enough? There are a variety of situations that can make it difficult or unreliable to make this assessment based on looking at metrics and lift alone. Inadequate audience/sample sizes, the presence of a few big outliers, and/or an inordinate percentage of your control group happening to be in the Bahamas during your experiment are just a few examples of issues that may lead to misinterpreting the likelihood that a given incremental benefit will be replicable in the future.\n\n**Significance testing is the statistical methodology used to assess how likely it is that an observed difference in performance between a treatment and control group is not due to random chance**.\n\nIt helps give us confidence that the observed difference is actually due to the intervention on the treatment group, and therefore if we continue outreach to this audience using the intervention, we will continue to observe a similar effect.\n\nThe two primary measures used to calculate statistical significance are the metric in question and the audience sizes (referred to as sample size). In both cases, more is typically better. If the observed difference between treatment and control (effect size) is large, statistical significance may be reached even for a campaign with a small sample size. Similarly, if the sample size for an audience is very large, we are more likely to be able to conclude that even a small performance difference between treatment and control is not due to chance. (Note that just because a small performance difference is not due to chance, it doesn't necessarily indicate that it was worth the cost to achieve it!)\n\n‍\n\nWhen statisticians talk about statistical testing, it is framed in terms of what is called the null hypothesis. The experimenter's hypothesis is that the treatment intervention is going to have a real impact on the behavior of those who receive it. The null hypothesis, conversely, is the opposite - the base assumption that any difference in treatment vs. control is due to random chance. Significance testing, therefore, is used in an attempt to _reject_ the null hypothesis.\n\nSignificance tests always come hand in hand with something called Confidence Intervals. If you've worked with significance testing in the past, you've probably heard something along the lines of... \"The effect is significant at a Confidence Interval of 95% or .95.\" This is another way of saying that there is at least a 95% chance that the observed effect is not due to chance. The Confidence Interval represents the probability threshold at which the experimenter is willing to reject the null hypothesis. The higher the Confidence Interval, the more difficult it is to reach statistical significance. Larger effect sizes and sample sizes both contribute to higher statistical confidence.\n\nFundamentally, the decision of what Confidence Interval to use is made by the experimenter, or often the organization or marketing department as a whole. There is no right or wrong way to make this determination - it's based on how much tolerance one has for the risk of incorrectly rejecting the null hypothesis, which often depends on the nuances of the experiment or business context. Academic researchers, for example, often have to go through a rigorous review process before their work is accepted for publication by a journal, and as such generally demand a high level of confidence in their findings. Confidence Intervals of 95% or even 99% are often used. When evaluating marketing or sales campaigns, however, statistical confidence can be harder to come by and the stakes of getting it wrong are generally far less. As such Confidence Intervals of 90% or even 80% are not uncommon.\n\n‍\n\nThere is a large variety of Significance Tests that have been developed for this type of experimental validation. This variety exists to handle the nuances presented by different experimental frameworks and metrics.\n\nGrowthLoop defaults to the use of just a few tests in our campaign evaluation framework:\n\n* **t-test / z-test:** Parametric tests used to compare two sample means when evaluating normally distributed metrics\n* **Mann-Whitney U test:** Non-Parametric test used to compare samples that are not normally distributed.\n\n‍\n\n* * *\n\nIn this article, we will provide step-by-step instructions for how to view our most commonly requested metric - Revenue Uplift - as part of GrowthLoop Campaign Evaluation.\n\n‍\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd84151181c9cc_Screen%20Shot%202021-10-28%20at%209.44.31%20AM.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd84151181c9cc_Screen%20Shot%202021-10-28%20at%209.44.31%20AM.png)\n\nIn order for Campaign Evaluation to begin, you must have an exported audience with a treatment/control split that has some percentage of customers in each group. You can quickly check which audiences fit this criteria when you open up Audience Builder and search through your saved audiences on the home page. The 'Status' column must show 'Exported' and the 'Treatment / Control' column must show any split that isn't 100%/0% (indicating that you exported the audience with zero customers in the control group).\n\nOnce you have identified a qualifying audience and would like to analyze its associated Campaign Evaluation, simply click the audience name to open up the audience.\n\n‍\n\n**Step 2: Scroll to the 'Performance' graph that populates for all qualifying audiences**\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd84ebb281c9c2_Screen%20Shot%202021-10-28%20at%209.50.34%20AM.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd84ebb281c9c2_Screen%20Shot%202021-10-28%20at%209.50.34%20AM.png)\n\nThis 'Performance' graph is your window into GrowthLoop Campaign Evaluation. This graph will quickly identify the total number of customers that have entered your audience over time, along with the performance over time of the selected Metric and Value Type.\n\nThe above screenshot reveals that 2,494 customers has qualified for the example audience over time, based off the Flex Filters applied in Audience Builder. The Metric selected is 'Customer Count' and the Value Type is 'Total', revealing a time graph of the total number of customers entering or exiting this audience over time. We can click the dropdown boxes in the upper right hand corner to change the visible Metric and Value Type.\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd84003381c9cb_Screen%20Shot%202021-10-28%20at%209.56.24%20AM.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd84003381c9cb_Screen%20Shot%202021-10-28%20at%209.56.24%20AM.png)\n\n_Please note: these Metric options are entirely configurable to fit your needs. Since we hook directly into your data warehouse, we can provide customer performance evaluation on any number of metrics available. This can include revenue, app logins, email opens, opportunities won, etc. Please[reach out](mailto:solutions@GrowthLoop.com) if you have any questions or need different Metrics enabled for your Audiences!_\n\n‍\n\nIn order to analyze Revenue performance of an audience, we must first select the Revenue metric from the Metric dropdown box. This will reveal Revenue totals for the Treatment, Control, and Adjusted Control groups over time.\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd840cb381c9c8_Screen%20Shot%202021-10-28%20at%2010.24.48%20AM.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd840cb381c9c8_Screen%20Shot%202021-10-28%20at%2010.24.48%20AM.png)\n\nSince the treatment/control split for the example audience above heavily favored treatment sizing over control, it is expected to witness overall greater revenue totals out of the Treatment group (blue) vs. the Control group (red). But in order to perform an 'apples-to-apples' comparison of these groups, we appropriately scale the Control group's revenue to equate to the number of customers in the Treatment group, resulting in the calculated Adjusted Control (green) performance. The Uplift generated is effectively the difference between the Treatment group and the Adjusted Control Group.\n\n‍\n\nTo graphically see the difference in these two curves as a calculated Uplift metric, all you need to do is select 'Uplift' in the Value Type dropdown box.\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd849dc081c9bb_Screen%20Shot%202021-10-28%20at%2010.32.42%20AM.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd849dc081c9bb_Screen%20Shot%202021-10-28%20at%2010.32.42%20AM.png)\n\nAssuming your campaign is 'successful' like the example audience shown, you will have a calculated Revenue Uplift total presented to you upon selecting 'Metric: Revenue' and 'Type: Uplift' from the dropdown boxes! Check back frequently to observe how this performance changes over time. If the campaign is successful, you should expect to see a positive uplift that hopefully grows over time, indicating that this could be an effective audience to target for future campaigns as well.\n\nIt should go without saying that, in reality, there are _MANY_ variables and metrics to consider in determining if a campaign is truly successful or not. Revenue, while often an important metric, is just one of these variables to ultimately consider.\n\nWith GrowthLoop Campaign Evaluation, you have the power to quickly observe if Revenue Uplift is being generated via your experimental audience by comparing the treatment vs. control groups. This, combined with the ability to experiment and learn quickly, are just a few of the many reasons our clients have chosen GrowthLoop services.\n\nLet's say you launch an experimental audience and begin seeing revenue performance that looks like the following:\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd840e4b81c9c7_Screen%20Shot%202021-10-28%20at%2010.43.19%20AM.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd840e4b81c9c7_Screen%20Shot%202021-10-28%20at%2010.43.19%20AM.png)\n\nFrom the above graph, we can observe that the Treatment group was outperforming the Adjusted Control group for some time, but then suddenly that performance reversed over the course of about 2 weeks. Now the Adjusted Control is generating greater total revenues than the treatment. The reason for 'why' this happens is not always obvious and may require further investigation. But ultimately we must be realistic that this specific campaign may not be generating revenue lift any further. This doesn't mean you are 'losing money', but rather that the Control group is now spending relatively more than the Treatment group for whatever reason. The resulting Uplift graph would then resemble:\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd846d7481c9d3_Screen%20Shot%202021-10-28%20at%2010.47.29%20AM.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd846d7481c9d3_Screen%20Shot%202021-10-28%20at%2010.47.29%20AM.png)\n\nWhile this result may be disappointing to observe at first, it is important for the growth of your sales and marketing teams to observe and learn quickly. This may indicate that the selling efforts and/or creative is not as effective with the target audience as initially expected and empowers your teams to test and pivot faster than they likely could before.\n\n* * *\n\nCampaign evaluation is a crucial step in the marketing process to determine the effectiveness of your campaigns. At GrowthLoop, we understand the importance of gaining insights from your marketing endeavors. That's why we offer a powerful Automated Campaign Evaluation Service, allowing you to not only assess your ongoing campaigns but also retrospectively measure their performance. In this guide, we will explore into what this service entails, its benefits, and provide you with a detailed, step-by-step tutorial on enabling Campaign Evaluation to elevate your marketing strategies.\n\nCampaign evaluation involves assessing the performance and impact of your marketing campaigns. It helps you answer questions like:\n\n* Did my campaign lead to increased sales or conversions?\n* How much revenue did my campaign generate?\n* Would customers have made purchases without the campaign?\n\nGrowthLoop's automated campaign evaluation service allows you to perform statistical A/B testing, helping you compare the behavior of a treatment group (those exposed to your campaign) with a control group (those not exposed to the campaign) to measure the true impact of your marketing efforts.\n\nGrowthLoop's campaign evaluation service offers several advantages:\n\n* **Automation**: The service is fully automated, eliminating the need for manual intervention.\n* **Data Warehouse Compatibility**: The service is compatible with various data warehouses, making it adaptable to your specific infrastructure.\n* **Cost-Effective**: It offers cost savings as it only evaluates audiences when explicitly activated and for a specified time period.\n\nBefore diving into campaign evaluation, it's important to understand two types of metrics:\n\n* **Count Metrics:** These metrics count specific actions taken by customers, such as the number of customers who attended an event or made a purchase. It focuses on conversions.\n* **Sum Metrics:** These metrics measure the total value of specific actions, such as the total revenue generated from purchases. They detect uplift rather than conversion.\n\nHere's a step-by-step guide on how to setup Campaign Evaluation using GrowthLoop:\n\n**Note**: Contact your Solutions Architect Manager to enable Campaign Evaluation in your account!\n\n‍\n\n**Step 1: Make sure you have an exported audience with a treatment/control split.**\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/64f8d02e2858785bfb70e032_Screenshot%202023-09-06%20at%203.13.41%20PM.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/64f8d02e2858785bfb70e032_Screenshot%202023-09-06%20at%203.13.41%20PM.png)\n\nTo start the Campaign Evaluation process, it's essential to have an audience that has been exported and divided into treatment and control groups with some customers in each group. You can easily verify if you have such audiences by going to Audience Builder and checking your saved audiences on the home page. Look for audiences with a 'Status' of 'Exported' and a 'Treatment / Control' split that isn't 100%/0%, which indicates that there are customers in both groups.\n\n**Note:** Learn how to setup a treatment/control split for an audience [here](https://docs.growthloop.com/docs/experiments).\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/64f8d055f1af38addff3cf5a_Screenshot%202023-09-06%20at%203.13.57%20PM.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/64f8d055f1af38addff3cf5a_Screenshot%202023-09-06%20at%203.13.57%20PM.png)\n\nChoose the dataset type **Transactions** or **Events**.\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/64f8d06e221daad71a9a7f7d_Screenshot%202023-09-06%20at%203.14.15%20PM.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/64f8d06e221daad71a9a7f7d_Screenshot%202023-09-06%20at%203.14.15%20PM.png)\n\nChoose the **dataset** and **table** that houses the metric you wish to evaluate. In this example, we will be connecting to the \"total\\_spend\" table, which holds the data pertaining to the total revenue generated from customer purchases.\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/64f8d0939f3f2b84be8bc4d8_Screenshot%202023-09-06%20at%203.14.29%20PM.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/64f8d0939f3f2b84be8bc4d8_Screenshot%202023-09-06%20at%203.14.29%20PM.png)\n\n‍\n\n**Important —** Next, label your data set by specifying columns such as:\n\n* **date of the transaction**\n* **revenue**\n* **unique identifier** (e.g., transaction ID).\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/64f8d0b410506043b96a6e50_Screenshot%202023-09-06%20at%203.14.41%20PM.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/64f8d0b410506043b96a6e50_Screenshot%202023-09-06%20at%203.14.41%20PM.png)\n\n‍\n\nFinally, join the transaction table to your user table by specifying the join key and click **Create**.\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/64f8d0cbf3b4a6becf2f1bcf_Screenshot%202023-09-06%20at%203.14.54%20PM.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/64f8d0cbf3b4a6becf2f1bcf_Screenshot%202023-09-06%20at%203.14.54%20PM.png)\n\nNavigate to the **audience** you want to analyze its Campaign Evaluation.\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/64f8d100ab91e8b7e5570f71_Screenshot%202023-09-06%20at%203.15.15%20PM.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/64f8d100ab91e8b7e5570f71_Screenshot%202023-09-06%20at%203.15.15%20PM.png)\n\n‍\n\nSelect the **Performance** tab and specify the **Evaluation End Date**.\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/64f8d11badf7d1384bd2a25f_Screenshot%202023-09-06%20at%203.15.28%20PM.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/64f8d11badf7d1384bd2a25f_Screenshot%202023-09-06%20at%203.15.28%20PM.png)\n\n‍\n\nAfter the evaluation runs, select the metric in the **Metric drop-down** box and you will see the audience performance data.\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/64f8d1310a143e79aa549286_Screenshot%202023-09-06%20at%203.15.46%20PM.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/64f8d1310a143e79aa549286_Screenshot%202023-09-06%20at%203.15.46%20PM.png)\n\nThe **Performance** graph serves as your portal into the GrowthLoop Campaign Evaluation. This graph provides a swift overview of the cumulative count of customers entering your audience over time. Additionally, it showcases the performance trend of the chosen Metric and Value Type over time.\n\nGrowthLoop's automated campaign evaluation service streamlines the process of assessing the impact of your marketing campaigns. By enabling statistical A/B testing, you can measure the true uplift your campaigns generate. Whether you have treatment and control groups or not, GrowthLoop's service provides valuable insights into your marketing efforts, helping you make data-driven decisions and optimize your campaigns for success.\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:24.973Z","d83e7e74-580d-433d-b2de-61b4440a3378",[],[],{"_40":807,"_128":808,"_130":809,"_132":810,"_134":-5,"_13":-5,"_120":811,"_122":136,"_25":812,"_138":-5,"_139":813,"_141":814},"How to set up BigQuery as a destination | GrowthLoop Docs","how-to-set-up-bigquery-as-a-destination-growthloop-docs","https://docs.growthloop.com/docs/bigquery-destination","# How to set up BigQuery as a destination\n\nThis article outlines the steps necessary to set up BigQuery as a GrowthLoop destination and begin exporting audiences for activation.\n\nTo connect the GrowthLoop application to BigQuery, we need the following:\n\n* Access to a BigQuery Data warehouse\n* Google Cloud service account (and its account key saved as a JSON file)\n\nIf you already have a service account and have stored its key as a JSON file, you can skip to **Setting BigQuery as a Destination.**\n\nIn order to create a service account for your project, you will need the **serviceAccountAdmin** and **BigQuery Admin** permissions. If you are unsure whether you have these permissions, check with your Google Cloud Platform administrator.\n\nFrom the GCP homepage, use your quick search bar to find **Service Accounts.**\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd84489281caaa_Untitled.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd84489281caaa_Untitled.png)\n\nChoose **Create Service Account.**\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd84d50881caa7_Untitled.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd84d50881caa7_Untitled.png)\n\nProvide identification and description details for your service account, then click **Create and Continue**.\n\n* **Service Account Name:** A descriptive name for your service account. If your name includes multiple words, separate them with dashes.\n* **Service Account ID:** GCP will auto-populate this field. Below it, an email address associated with your service account will appear.\n* **Service Account Description:** A short description of the purpose of your service account.\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd849b4b81caa9_Untitled.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd849b4b81caa9_Untitled.png)\n\nGrant your service account access to your project with the **Editor** role and click **Done.**\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd84ba6081cab2_Untitled.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd84ba6081cab2_Untitled.png)\n\nJSON keys are files that allow external services like GrowthLoop to engage with your service account. If you already have a JSON key for your service account, skip to **Setting BigQuery as a Destination**. If you do not, create a new one using the steps below. Save your JSON key file in a safe and memorable place - this key is not recoverable, and you will need to create another if you lose it. You have a limit of 10 keys per service account.\n\nTo create a key, you need to have administrative privilege over keys for your project. If you receive a permissions error during the key setup process, ask your Google Cloud administrator to either 1) provide you with key creation permissions, or 2) create the key themselves and provide you with the JSON.\n\nFirst, log in to your Google Cloud Platform account. In the **Search** bar, type “Service Accounts” and select **Service Accounts** from the dropdown.\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd84be6f81caa5_Untitled.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd84be6f81caa5_Untitled.png)\n\nFind and click into the correct service account.\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd84424f81ca9d_Untitled.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd84424f81ca9d_Untitled.png)\n\nNavigate to **Keys.** Choose **Create New Key** from the **Add Key** dropdown.\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd84483081caa1_Untitled.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd84483081caa1_Untitled.png)\n\nSelect **JSON** and click **Create.** The new key file will automatically download to your computer as a JSON file. Save the file in a secure, memorable place.\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd84e9ca81caa0_Untitled.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd84e9ca81caa0_Untitled.png)\n\nNow that you have a service account and service account key, you are ready to set BigQuery as a destination!\n\n1. Select **Destinations** from the left rail of your GrowthLoop home screen.\n2. Click **New Destination** on the top right.\n3. Scroll down to the **Data Warehouse** section and click **Add BigQuery**.\n4. A modal window will prompt you to fill out **Destination Info** and **Credentials**.\n 1. **Destination Name:** A custom name for your destination.\n 2. **Sync Frequency:** The frequency at which GrowthLoop will export audiences to your destination (hourly or daily).\n 3. **Dataset:** The BigQuery dataset where you want your new table to live.\n 4. **Table Name:** A name for the table GrowthLoop will create in BigQuery.\n 5. **Credentials:** Copy and paste the entire contents of your JSON key file here.\n 6. **Columns to Export:** Columns that will be exported by default when you export an audience to BigQuery. Use the column names of the underlying datasets in your data warehouse. If you do not specify any column names, all columns will be exported by default.\n5. Click **Create.** You are now ready to begin exporting to your Google Cloud Storage destination! You can confirm that BigQuery is connected by clicking **Destinations** on the left rail.\n\nWhen exporting to BigQuery, you will be prompted select an **Export Type** and **Personalization Fields**.\n\n* **Export Type:** Choose between **Export All Records** and **Export Updates (Deltas).**\n* **Export All Records:** Each time your audience exports, a new record is created for every member of the audience.\n* **Export Updates (Deltas):** Each time your audience exports, a new record is only created for _new_ members of the audience.\n* **Personalization Fields:** By default, GrowthLoop will export only the columns specified during destination setup (called **Columns to Export**). If you would like to add any additional columns to your export, do so here.\n\nAfter exporting, your table will appear nested within the dataset you specified during destination setup.\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:37.004Z","92265ed5-7afa-435a-8e15-62c63d74a9c2",[],[],{"_40":816,"_128":817,"_130":818,"_132":819,"_134":-5,"_13":-5,"_120":820,"_122":136,"_25":821,"_138":-5,"_139":822,"_141":823},"How to set up Braze as a destination | GrowthLoop Docs","how-to-set-up-braze-as-a-destination-growthloop-docs","https://docs.growthloop.com/docs/braze-destination","# How to set up Braze as a destination\n\nIn this tutorial, you’ll set up Braze as a destination platform.\n\nIn this tutorial, you’ll set up Braze as a destination platform, which enables you to export audiences to Braze to support marketing campaigns. Before connecting Braze to the GrowthLoop application, we will walk through the requirements below:\n\n* Configure Braze Rest API Key\n* Define API URL\n\nBefore connecting the GrowthLoop application to the Braze destination, you will need to create a new REST API key. In the Braze UI, scroll to the bottom of the left hand options, and select **Developer Console**.\n\n![](https://files.readme.io/a2524af-braze_developer_console.png)\n\nIf you have an available REST API key, feel free to use that. However, we recommend creating a new API key by clicking **Create New API Key** in the Rest API Keys section. \\*\\*\\*\\*\n\n![](https://files.readme.io/a783741-braze_create_api_key.png)\n\nGive your new API key a name, like **GrowthLoop API Key**, and provide all the permissions offered to the API key. Note: click the checkbox in the grey headers to select all permissions within a section, instead of 1-by-1 manually selecting each. When you reach the bottom, click **Save API Key**. You don’t need to whitelist the IP.\n\n![](https://files.readme.io/2a9681e-braze_api_key_name.png)\n\nYou will return to the API keys section. Scroll down to see the new API key you just generated. Copy and save the “identifier”. This will be needed next to connect the destination to the GrowthLoop application.\n\n![](https://files.readme.io/1aaf30c-braze_view_api_key.png)\n\nTo connect to Braze in the GrowthLoop application, you will need to know the API URL. In the Braze UI, scroll down to the bottom of the menus on the left and click on **Manage Settings**. On the right hand side, see **SDK Endpoint**. In the example below, you can see `sdk.iad-03.braze.com`.\n\n![](https://files.readme.io/bced292-view_braze_api_url.png)\n\nIn another tab, visit this [Braze API Overview](https://www.braze.com/docs/api/basics/#endpoints) website. Scroll down to the **Endpoints** section, and find the URL that matches your Braze URL. Copy the **Rest Endpoint** for your instance and save it somewhere easily accessible. In the example we are using, the SDK Endpoint contains `-03`, and therefore the instance to be used is US-03. The Rest Endpoint / API URL would then be `https://rest.iad-03.braze.com`.\n\nWhen you sign into the Segmentation Platform, navigate to the **Destinations** tab on the left sidebar and click **New Destination** in the top right corner.\n\n![](https://files.readme.io/894949a-select_destinations_navigation.png)\n\nScroll until you can find Braze, and click **Add Braze**.\n\n![](https://files.readme.io/2a828e2-add_braze_destination.png)\n\nA popup will appear to configure the connection to the destination.\n\n* **Destination Name:** This is how the destination will be named and referred to in the app going forward.\n* **Sync Frequency:** Select Daily or Hourly, this will control how often GrowthLoop exports audiences to Braze.\n* **API Key**: API key created in the requirements, with the necessary permissions.\n* **API URL**: URL as defined in the requirements. To find the correct API URL, refer to this [table](https://www.braze.com/docs/api/basics/#braze-rest-api-collection) to match the URL of the dashboard you use with the corresponding REST Endpoint.\n\n![](https://files.readme.io/7828e2b-add_destination_config_braze.png)\n\nClick **Create** and you are ready to export your first audience to Braze!\n\nAfter you have exported an audience to the Braze destination, navigate to the Braze UI. Log in to the account, and under **Segments**, select **Custom Attributes** as a filter. Look at the options within Customer Attributes, and you'll find the audience list that you exported.\n\n![](https://files.readme.io/587138d-select_braze_audience.png)\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:37.152Z","5c84644d-2d78-4c70-9435-eb649a26ae58",[],[],{"_40":825,"_128":826,"_130":827,"_132":828,"_134":-5,"_13":-5,"_120":829,"_122":136,"_25":830,"_138":-5,"_139":831,"_141":832},"How to set up CM360 as a destination | GrowthLoop Docs","how-to-set-up-cm360-as-a-destination-growthloop-docs","https://docs.growthloop.com/docs/campaign-manager-360","# How to set up CM360 as a destination\n\n## Google Campaign Manager 360 Conversions\n\nLearn how to connect and send Conversions to Google Campaign Manager 360 (CM360)\n\nIn this article, we'll guide you through connecting `Campaign Manager 360 (CM360)` to GrowthLoop and syncing conversions to the destination.\n\n`Campaign Manager 360 (CM360)` is a Google Marketing Platform tool used to track and manage digital ad campaigns, including sending and attributing conversions back to ads for accurate performance measurement.\n\nGrowthLoop enables syncing to the following object:\n\n| Object | Description | Sync Modes | Field Mappings (Required) | Field Mappings (Optional) |\n| --- | --- | --- | --- | --- |\n| `Conversion` | Sync and track offline behavior | Insert (adds new events) | `Floodlight Activity ID`: The ID that identifies where you want to send your conversions.

`Timestamp`: The exact date and time of the conversion.

`User Identifer`: The unique identifier assigned to a click (e.g., Google Click ID). | See full list of parameters [here](https://developers.google.com/doubleclick-advertisers/guides/conversions_overview) |\n\n* Add our production service account to your **Ad Manager** network: \n `google-integrations@flywheel-prod-328213.iam.gserviceaccount.com` [Click here for step-by-step instructions](https://developers.google.com/ad-manager/api/authentication#configure) on how to configure service account access.\n* Have your **Profile ID** ready. This seven-digit number defines your access permissions and scope within a specific CM360 account. You can find it by logging into your CM360 account, navigating to the Admin section, and selecting User Profiles - your assigned Profile ID will be listed there.\n* Have your **Floodlight Activity ID** ready. You can either apply the same ID to all rows during the sync by specifying it in the [Setup Destination](https://docs.growthloop.com/docs/campaign-manager-360#/setup-destination) page, or dynamically assign a different ID to each row by mapping a column from your dataset on the [Sync Field Mapping](https://docs.growthloop.com/docs/campaign-manager-360#/set-up-a-sync) page.\n\n1. Log into **GrowthLoop** and click the **Destinations** tab on the left sidebar.\n \n2. Then click **New Destinations** on the upper right side.\n \n3. Next, search for **Campaign Manager 360** in the destination modal and click **Add Campaign Manager 360**.\n \n4. Enter the required information in the modal, then click **Create**.\n \n 1. `Destination`: Enter the name you want to give the destination.\n 2. `Sync Frequency`: Select a default export frequency to the destination.\n 3. `Profile ID (Required)`: Enter the seven-digit number defines your access permissions and scope within a specific CM360 account.\n 4. `Floodlight Activity ID`: Enter the Activity ID where you want to send your conversions. This is optional if you prefer to dynamically assign a different ID to each row. See [Sync Field Mapping](https://docs.growthloop.com/docs/campaign-manager-360#/set-up-a-sync) section for details.\n\n5. Click **Syncs** on the left sidebar.\n \n6. Then click **Create Sync** on the upper right hand-side.\n \n7. Next, configure your sync by filling out the following fields:\n \n 1. Route Name:\n \n 1. **Name:** A friendly name for the sync.\n 2. Source:\n \n 1. **Dataset/Table:** The table that holds the data you want to sync. Usually, it's organized within an events table.\n 2. **Dataset Unique Field(s):** The unique field(s) on the table. They will populate automatically after selecting the Dataset/Table.\n 3. **Match Field**: The user identifier used to match and identify conversions from your source table in the destination (e.g., Google Click ID).\n 3. Destination:\n \n 1. **Connection:** The destination you will sync data to. Please select **Campaign Manager 360**.\n 2. **Object Type:** The object that you want to send data to. Please select **Conversion**.\n 3. **Match Field:** The user identifier used to match and identify conversions from the destination in your source table (e.g., Google Click ID).\n 4. Sync Settings\n \n 1. Sync Frequency\\*\\*: The default frequency for syncing data to the destination. The options are: **Fifteen minutes**, **Thirty minutes**, **Hourly**, **Daily**, **Weekly**, and **Monthly**.\n 2. **Update Rule:** The default operation for syncing data to the destination. Please select **Insert only**.\n8. Once you finish selecting/inserting the required fields, click **Save Sync**.\n \n9. Next, set up the field mappings to start your sync. `CM360` needs at least three of the following fields mapped: **Floodlight Activity ID**, **Timestamp**, and the same **user identifier** used to set up the sync.\n \n\n> 📘\n> \n> * If Floodlight Activity ID is set in the destination setup, you don't need to map it.\n> * The column you map to Timestamp will also be used as the ordinal for deduplicating conversions. To use a custom value for ordinal, you can map a separate column.\n> * Quantity is automatically set to \"1\" for each conversion you want to sync. To use a custom value, you can map a separate column.\n> * Encrypted user ID and candidates are not supported user identifier types.\n\n10. Let's begin with **Floodlight Activity ID**. Choose the field from your table that contains the Activity ID where you want to send your conversions.\n11. Then, under the Destination section, choose **Floodlight Activity ID** from the drop-down menu, unless it has been automatically selected for you.\n12. Next up, let’s map **Timestamp**. Pick the field from your table that contains the date and time of the conversion.\n\n> 📘\n> \n> GrowthLoop will convert any provided timestamp format into **Unix epoch** time in microseconds.\n\n13. Then, under the Destination section, choose **Timestamp** from the drop-down menu, unless it has been automatically selected for you.\n14. Lastly, choose the field in your source table that contains the user identifier associated with the conversion, and map it to the destination.\n\n> 📘\n> \n> Must be the same **user identifier** used to set up the sync.\n\n15. After clicking **Update Sync**, GrowthLoop will validate the information you provided. If everything looks good, your sync will be saved, and you can enable it by **toggling** the switch in the top-left corner of the page.\n\n> 👍\n> \n> You've successfully created a conversion sync to `CM360`!\n\n> 📘\n> \n> If you experience any issues when connecting to `Google Campaign Manager 360 Conversions`, please reach out to us at [support@growthloop.com](mailto:support@growthloop.com), and we’ll be in touch shortly to help resolve the matter!\n\nUpdated 3 months ago\n\n* * *","2025-10-23T18:20:51.709Z","1758aeab-376d-4e1d-86c0-070c58b2eeb0",[],[],{"_40":834,"_128":835,"_130":836,"_132":837,"_134":-5,"_13":-5,"_120":838,"_122":136,"_25":839,"_138":-5,"_139":840,"_141":841},"How to set up default filters | GrowthLoop Docs","how-to-set-up-default-filters-growthloop-docs","https://docs.growthloop.com/docs/setup-default-filters","# How to set up default filters\n\nIn this article you'll learn how to set up default filters on your audience canvas.\n\nAt GrowthLoop, we aim to make it extremely easy for any users on your team to leverage your company's data for marketing and sales. To empower your teams to leverage your data, it is important to set them up for success in the GrowthLoop platform. We make this easy through a few different capabilities like:\n\n* **[Templates](https://docs.growthloop.com/docs/audience-recipes-templates):** Audience templates can help your team members get started with criteria and values already set for a particular audience and then build on top of that template. For example, many customers create templates for things like \"Churned Customers,\" so everyone uses the same data to define that segment in the company.\n* **Field Aliasing and Descriptions:** In GrowthLoop, you can add field aliases and descriptions to your datasets to help marketers understand the filters they are using while building an audience.\n* **Default Filters:** In GrowthLoop, you can help your team members by giving them default fields on the audience canvas every time they start a new audience. GrowthLoop customers often use default filters to show team members commonly used fields to build audiences so they don't have to start with a blank slate.\n\nYou can set up default filters for each dataset group in GrowthLoop. Here is how to get started.\n\n1. Select `Datasets` on the left-hand menu\n2. You should see the `Dataset Groups` tab highlighted\n3. Select the `Dataset` tab\n4. Select the `Primary`dataset (also known as the Users dataset) that you would like to enable default filters for.\n5. Scroll down to the Table Configuration section.\n6. You should see all the filters available from this dataset in the Field Manager table.\n7. Each field in the table has a `Show by Default` checkbox. By selecting the checkbox, you are enabling that field to show by default on your builder.\n8. Click Save\n\n> 📘\n> \n> We usually recommend 5-10 of your most commonly used attributes to be designated as default fields. This empowers your team members to get started with their audience quickly, while not overwhelming them with options.\n\nOnce you have set your default filters, every user that creates a new audience with the `Dataset Group` with the `Primary` dataset will see those default filters as immediate options to us on the audience canvas.\n\n1. Select New Audience\n2. Select `Dataset Group` that contains the `Primary` dataset.\n3. You can now see your Default Filters already on the audience canvas ready to use\n\n![](https://files.readme.io/4b66f2b-Screenshot_2024-05-08_at_10.07.48_AM.png)\n\nWe hope you found this helpful. If you have any questions, please don’t hesitate to reach us at [support@growthloop.com](mailto:support@growthloop.com).\n\nUpdated 5 months ago\n\n* * *","2025-06-20T22:58:10.560Z","e66e7680-8971-4cca-ae48-8886c3150b4a",[],[],{"_40":843,"_128":844,"_130":845,"_132":846,"_134":-5,"_13":-5,"_120":847,"_122":136,"_25":848,"_138":-5,"_139":849,"_141":850},"How to set up DV360 as a destination | GrowthLoop Docs","how-to-set-up-dv360-as-a-destination-growthloop-docs","https://docs.growthloop.com/docs/display-and-video-360","# How to set up DV360 as a destination\n\n## Google Display & Video 360\n\nLearn how to connect and send audiences to Display & Video 360 (DV360)\n\nDiscover how to link **Display & Video 360 (DV) 360** as your destination and unleash the power of exporting audiences across Google's ad channels – from Gmail and Google Display to Video and Connected TV.\n\nBefore connecting **DV360** to the GrowthLoop application:\n\n* You must have a **DV360** account to connect to the GrowthLoop application. If you do not, contact their [sales team](https://marketingplatform.google.com/about/display-video-360/).\n* Ensure you have an account for your GrowthLoop Audience Platform. If you don't, reach out to the admin at your company, or [support@growthloop.com](mailto:support@growthloop.com) and we'll help you get sorted.\n\n1. In **DV360**, expand the **Advertiser Settings** menu (▼) in the left hand panel.\n \n2. Click on **Linked Accounts**, and then click on **LINK NEW ACCOUNT**.\n \n3. Select **External Data Partner** from the drop down menu.\n \n\n> 📘\n> \n> Depending on what products/features you have access to, the options may look different.\n\n4. Use the search box to search for **CMU: GrowthLoop**.\n5. Click on the link button and accept the terms to complete the product link.\n6. Congrats! You just linked your **DV360** account to GrowthLoop **[🎉](https://emojipedia.org/party-popper)**\n\n7. Log into **GrowthLoop** and click the **Destinations** tab on the left sidebar.\n \n8. Then click **New Destinations** on the upper right side.\n \n9. Next, search for **Display & Video 360 (DV360)** in the destination modal and click **Add Display & Video 360 (DV360)**.\n \n10. Enter the required information in the modal, then click **Create**.\n \n 1. `Destination`: Enter the name you want to give the destination.\n 2. `Sync Frequency`: Select a default export frequency to the destination.\n 3. `Display & Video 360 Advertiser ID`: Enter the advertiser ID where you want to export your audiences. To locate it, sign in to Display & Video 360 > in the navigation menu, click Advertiser Settings to expand it, then click Basic Details > find your Advertiser ID at the end of the first section.\n\n11. To export an audience, navigate to an audience and click **Export**.\n12. When the **Create Export** window pops up, type **Display & Video 360** into the search bar and click **Select.**\n13. By default, the name field will auto populate to your audience name so you can easily find it in your destination. You can then select your:\n 1. campaign type\n 2. export schedule\n 3. sync end date\n 4. personalization fields\n 5. user consent data mappings\n\n> 📘\n> \n> If your customers are based in EEA (Economic European Area) or UK, we highly recommend you map the required consent fields to their corresponding columns on your Users dataset. This will ensure Google to include them as part of your targetable audiences.\n\n14. Click the **Match Fields** pill menu and choose your match fields.\n\n> 📘\n> \n> GrowthLoop supports **array columns as match fields**. If your primary table contains a column with an array of identifiers (e.g., a list of email addresses), GrowthLoop can automatically expand the array and send each value individually to the destination. This helps improve match rates by ensuring that all valid identifiers are included in the export.\n\n15. Hit **Export** to start exporting your audience. You can then view your exported audience by logging into your DV360 Account and navigate to the `Audiences` section to view your audience!\n\n> 👍\n> \n> You have successfully exported your first audience to `DV360`!\n\nUpdated 3 months ago\n\n* * *","2025-06-20T22:58:40.210Z","e8b479d0-e180-495d-85dc-0e4220247d32",[],[],{"_40":852,"_128":853,"_130":854,"_132":855,"_134":-5,"_13":-5,"_120":856,"_122":136,"_25":857,"_138":-5,"_139":858,"_141":859},"How to set up email alerts on GrowthLoop","how-to-set-up-email-alerts-on-growthloop","https://docs.growthloop.com/docs/email-alerts","In this article, you'll learn how to set up Email Alerts in GrowthLoop.\n\nWe currently support the following notification types, but will be expanding to more types very soon:\n\n1. **Audience Export Failure** -- triggered every time an audience export fails.\n2. **Invalid Destination Connection Credentials** -- triggered as part of a daily process that checks if credentials are valid to connect to each destination. The notification for each destination will only be sent the first time we find the error, and then once a week until the credentials are fixed. It'll trigger again only if credentials are fixed and the daily process fails a second time later.\n3. **Dataset Update Failure** -- triggered as part of a daily process that checks the last time datasets were updated. We trigger two types of notifications:\n \n 1. A notification including datasets not updated in the previous 2 to 7 days (warning)\n 2. A notification including datasets not updated for more than 7 days (danger). Datasets will be included in further notifications if:\n \n * they are updated and then become outdated again\n4. **Audience Ready for Review** -- triggered when you've set audiences for a GrowthLoop team to be reviewed before they're ready to be exported. This is triggered when a user submits their audience for approval. For more details on the audience approval process, refer to [this doc](https://docs.growthloop.com/docs/audience-approval-process#approving-an-audience)\n\nYou can set up notifications to any desired email address, such as your work email or an alias for a group of users on GrowthLoop, by navigating to the **Organization menu, under the Notifications tab**.\n\n![](https://files.readme.io/146f6e1-image.png)\n\n**Here is how you get it set up:**\n\n1. Navigate to Organization --> Notifications tab\n \n2. Add the email address you'd like to be notified for the **notification type desired**\n \n3. Save your settings\n \n\nNow, every time that specific notification type is triggered, you'll receive an email from [Solutions@GrowthLoop.com](mailto:Solutions@GrowthLoop.com) that looks something like this, depending on the notification type. Below is an example of an **Audience Export Failure** notification type.\n\n![](https://files.readme.io/e9f3662-image.png)\n\nWe hope you find this feature useful. If you experience any issues or have any questions, please reach out to us at [support@growthloop.com](mailto:support@growthloop.com), and we’ll be in touch shortly!\n\nUpdated 5 months ago\n\n* * *","2025-06-20T22:58:45.687Z","a2e22356-b1db-4c99-809e-9efededafc95",[],[],{"_40":861,"_128":862,"_130":863,"_132":864,"_134":-5,"_13":-5,"_120":865,"_122":136,"_25":866,"_138":-5,"_139":867,"_141":868},"How to set up Facebook Ads as a destination | GrowthLoop Docs","how-to-set-up-facebook-ads-as-a-destination-growthloop-docs","https://docs.growthloop.com/docs/facebook-ads","# How to set up Facebook Ads as a destination\n\nIn this tutorial, you’ll set up Facebook as a Destination Platform for GrowthLoop audiences. Configuring Facebook as a Destination Platform enables you to serve ads across Facebook, Facebook Messenger, Instagram, and Whatsapp through their unified Ad Manager.\n\n1. Click **Destinations** in the left rail.\n\n![](https://files.readme.io/52c3917-Screenshot_2024-02-01_at_3.01.52_PM.png)\n\n2. Click **New Destination** on the top right corner, then search for and **Add Meta / Facebook Ads.**\n\n![](https://files.readme.io/02b0c2b-Screenshot_2024-02-01_at_2.59.15_PM.png)\n\n3. Log into Facebook with the business account associated with Facebook Ads Manager\n\n![](https://files.readme.io/fc111b7-Untitled_11.png)\n\n4. After providing permissions for GrowthLoop to access your Facebook Ads account, you will be returned to the screen below.\n 1. **Destination Name:** This how the destination will be named and referred to in the app going forward.\n 2. **Sync Frequency:** Please select Daily or Hourly, as this will determine how often GrowthLoop exports audiences to Facebook.\n 3. **Select Ad Account:** If you have multiple Ad Accounts, be sure to select the correct Account where GrowthLoop will export audiences to.\n\n![](https://files.readme.io/58fe1e8-image.png)\n\n5. Click **Create** and you are set to export your first audience to Facebook!\n\n6. To export an audience, you’ll need to build one first. Click **New Audience** and [Create your New Audience](https://docs.growthloop.com/docs/create-an-audience).\n \n ![](https://files.readme.io/453ab43-Untitled_4.png)\n7. Once you finish building the audience, click **Export Audience**.\n \n ![](https://files.readme.io/0157801-Untitled_5.png)\n8. When the **Create Export** window pops up, type **Facebook** into the search bar and click **Select**.\n \n ![](https://files.readme.io/7614f66-image.png)\n \n9. Then in the **Export Settings** tab, configure your desired **Export Name**, **Campaign Type** and **Export Schedule**. By default, the name field will auto populate to your audience name so you can easily find it in your destination\n \n ![](https://files.readme.io/e9edd41-Untitled_7.png)\n10. Next, configure your match fields in the **Match Fields** tab. We support **14** match fields. To optimize match rates, it's best to map as many of these as possible.\n \n ![](https://files.readme.io/c57d6fa-image.png)\n \n11. Lastly, click **Export**, and you're done! Congrats on successfully exporting an Audience to Facebook. To view the export, navigate to the **Audiences** tool on your Facebook ad account. You can locate this tool by typing “Audiences” into the quick search tool, located at the bottom left of your Facebook ad account.\n \n ![](https://files.readme.io/ebf7044-Untitled_13.png)\n\n> 📘\n> \n> When creating a **Campaign** with your business account, you will have the option to select **Manual Placements,** allowing you to direct your ads to Facebook, Instagram, and/or Messenger, amongst other customizations. For more information on creating and curating an ad campaign with Facebook, click [here](https://www.facebook.com/business/help/1420905584664062?id=274377816589261&ref=fbb_messenger_ads) .\n\nExperiencing any issues when connecting to Facebook? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and we’ll be in-touch shortly to help resolve the matter!\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:39.083Z","d263aa9e-a04a-49a4-b8f2-190be44e4830",[],[],{"_40":870,"_128":871,"_130":872,"_132":873,"_134":-5,"_13":-5,"_120":874,"_122":136,"_25":875,"_138":-5,"_139":876,"_141":877},"How to set up GAM360 as a destination | GrowthLoop Docs","how-to-set-up-gam360-as-a-destination-growthloop-docs","https://docs.growthloop.com/docs/google-ad-manager-360","# How to set up GAM360 as a destination\n\n## Google Ad Manager 360\n\nLearn how to connect and send audiences to Google Ad Manager (GAM) 360\n\nIn this article, we'll guide you through connecting Google Ad Manager (GAM) 360 to GrowthLoop and exporting your audiences to the destination.\n\nGAM 360 is an ad management platform publishers use to manage their ad inventory and maximize revenue.\n\n> ❗️\n> \n> * Get in touch with your Google account manager to enable audience lists via GCS for your network.\n> * Your Google account manager should also provide you with a public GCS bucket to receive audience lists, as well as configure an associated `Google Group` to manage permissions for this public bucket.\n> * The public bucket should have a URI in the format of: `console.developers.google.com/storage/browser/gdfp_cookieupload_[Ad Manager network code]`\n\n* Add GrowthLoop's service account: `google-integrations@flywheel-prod-328213.iam.gserviceaccount.com` as a user in your GAM 360 network. Make sure that API access is enabled and the account has permission to **View and Edit Audience Segments**. See [here for step-by-step instructions](https://developers.google.com/ad-manager/api/authentication).\n\n> 📘\n> \n> This prerequisite is only required if you want GrowthLoop to programmatically create a new audience segment during export. If you'd prefer to export audience members to an existing segment, you can simply specify the segment ID during the export setup. See **Step 11** for details. If you need to create a segment manually, you can learn how to do that [here](https://support.google.com/admanager/answer/2423498?hl=en&ref_topic=2423445&sjid=10383474665654025577-NC).\n\n* Locate your `network code`. Find it in Ad Manager under Admin, then Global settings, and then Network code.\n* If you have't already, create a Google Cloud Storage service account (refer to the [first half of this document on how to set it up](https://docs.growthloop.com/docs/google-cloud-storage#creating-a-service-account)). Ensure that this service account is added as a member to the `Google Group`with write access to the public GCS bucket set up by your Google account manager.\n\n1. Log into **GrowthLoop** and click the **Destinations** tab on the left sidebar.\n2. Then click **New Destinations** on the upper right side.\n3. Next, search for **GAM** in the destination modal and click Add **GAM360**.\n4. Enter the required information in the modal, then click **Create**.\n 1. `Destination Name`: Enter the name you want to give the destination.\n 2. `Sync Frequency`: Select a default export frequency to the destination.\n 3. `Bucket`: The name of your Google Cloud Storage bucket in the following format: `gdfpcookieupload[Ad Manager network code]`\n 4. `Credentials`: Copy and paste the entire contents of your JSON key file here.\n 5. `Network Code`: This is a unique identifier for your advertising network, which you can find in Ad Manager under `Admin > Global Settings > Network Code`.\n\n5. Navigate to your list of audiences by clicking the **Audiences** tab on the left sidebar.\n6. Choose an existing audience or create a new one.\n\n> 📘\n> \n> Need help creating audiences? Click [here](https://docs.growthloop.com/docs/create-an-audience) to learn how!\n\n7. Once created, click the **Export** button on the upper right side.\n8. Search for **GAM360** in the export modal and then click **Select**.\n9. In **Configure Match Field Settings**, click the drop-down and select one of the available match identifiers. Options include:\n * `Raw Publisher Provided Identifiers (PPID)` (Learn more about publisher provided identifiers [here](https://support.google.com/admanager/answer/2880055?hl=en&authuser=1).)\n * `Raw Identifier for Advertising (IDFA)`\n * `Raw Android TV Identifiers (ADID)`\n * `Raw Roku Identifiers (RIDA)`\n * `Raw Apple TV Identifiers (TVOS)`\n * `Raw Vizio Identifiers (VIDA)`\n * `Raw Samsung Identifiers (TIFA)`\\\\ \n \n\n> 📘\n> \n> No matter which identifier you choose, we check if the values are SHA-256 hashed (64-character hexadecimal digits). If they don’t pass our hash test, we hash them before sending to GAM360.\n\n> 📘\n> \n> GrowthLoop supports **array columns as match fields**. If your primary table contains a column with an array of identifiers (e.g., a list of email addresses), GrowthLoop can automatically expand the array and send each value individually to the destination. This helps improve match rates by ensuring that all valid identifiers are included in the export.\n\n10. Next, click the **Select values** drop-down and choose the corresponding field from your dataset that contains the selected identifier. This step is required to proceed.\n11. Configure your export settings:\n 1. `Export Name`: Automatically populated with your audience name for easy identification in the destination.\n 2. `Campaign Type`: Choose between **One Time** to export the audience once or **Ongoing** to continuously export new audience members as they qualify.\n 3. `Export Inclusion Criteria`: Choose between **All audience members** to export the full audience or **Newly added audience members** to export only those who have been added since the last export.\n 4. `Audience Segment ID`: Choose between **New** or **Existing**.\n 1. **New**: Selected by default, this option will create a new audience segment, using the audience name, and add users to the segment.\n 2. **Existing**: When selected, you're required to enter the unique ID of the target audience segment in GAM360. This action will add users to an existing audience segment.\n\n> 📘\n> \n> When a new audience is created, it will appear in GAM using the following format: `_GL_Audience_`. This is the standard naming convention we use to help you easily identify GrowthLoop-created audiences.\n\n12. `Export Schedule`: Configure the **Frequency**, **Start Date**, **End Date**, and specific **Days of the Week** (only for **Ongoing** exports).\n13. Finally, click **Export** to send the audience to GAM360!\n\n> 📘\n> \n> Expect up to a `24-hour delay` from segment creation to batch upload availability.\n\nWhile you wait, you can verify that the audience list has successfully landed in your GCS bucket. Look for a folder named in this format: `gdfp_cookie_upload__.csv`. Inside, you’ll find individual CSV files for each audience member.\n\n![](https://files.readme.io/f6ac360-gcs_audience_file.png)\n\n> 👍\n> \n> You have successfully exported the audience!\n\n> 📘\n> \n> Having trouble connecting or exporting to **GAM 360**? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com), and we’ll be in touch shortly to help resolve the issue!\n\nUpdated 3 months ago\n\n* * *","2025-06-20T22:58:41.475Z","fec764c1-d7d3-420e-9fbc-0f53f2141f57",[],[],{"_40":879,"_128":880,"_130":881,"_132":882,"_134":-5,"_13":-5,"_120":883,"_122":136,"_25":884,"_138":-5,"_139":885,"_141":886},"How to set up Google Ads as a destination | GrowthLoop Docs","how-to-set-up-google-ads-as-a-destination-growthloop-docs","https://docs.growthloop.com/docs/google-ads","# How to set up Google Ads as a destination\n\nLearn how to connect and send audiences to Google Ads\n\nIn this article, we'll guide you through connecting Google Ads to GrowthLoop and exporting your audiences to the destination.\n\nGoogle Ads is an online advertising platform where you can bid to display ads across Google’s search results, YouTube, and partner sites. It offers targeting options to reach specific audiences and optimize campaign performance.\n\n1. Log into **GrowthLoop** and click the **Destinations** tab on the left sidebar.\n \n2. Then click **New Destinations** on the upper right side.\n \n3. Next, search for **Google Ads** in the destination modal and click **Add Google Ads**.\n \n4. Sign in with your Google account that is connected to your Google Ads manager.\n \n5. Enter the required information in the modal, then click **Create**.\n \n 1. `Destination`: Enter the name you want to give the destination.\n 2. `Sync Frequency`: Select a default export frequency to the destination.\n 3. `Ad Account`: Select the ad account where you want to send audiences.\n 4. `GrowthLoop Managed Account` (Optional): Check the box if your Ads account is managed by GrowthLoop.\n 5. `Manager Account ID` (Optional): Leave this blank if you don't have a Manager Account or GrowthLoop manages your Google Ads account.\n 6. `Mobile App ID` (Optional): Enter the unique identifier for your mobile app. This is only required when uploading audiences using Device IDs.\n 1. For iOS: The 9-digit ID at the end of the App Store URL (e.g., 123456789).\n 2. For Android: The app’s package name (e.g., com.example.app).\n\n5. Navigate to your list of audiences by clicking the **Audiences** tab on the left sidebar.\n6. Choose an existing audience or create a new one. Need help creating? Click [here](https://docs.growthloop.com/docs/create-an-audience) to learn how!\n7. Once created, click the **Export** button on the upper right side.\n8. Search for **Google Ads** in the export modal and then click **Add Google Ads**.\n9. Select your **Match Type** and configure its associated match fields. By default, `Contact` is selected, but you can switch to `Device`. At least one match field must be filled out for export.\n10. Click **Next** and configure your export settings:\n 1. `Export Name`: Automatically populated with your audience name for easy identification in the destination.\n 2. `Campaign Type`: Choose between **One Time** to export the audience once or **Ongoing** to continuously export new audience members as they qualify.\n 3. `Export Inclusion Criteria`: Choose between **All audience members** to export the full audience or **Newly added audience members** to export only those who have been added since the last export.\n 4. `Mobile App ID`: Enter the unique identifier for your mobile app. This is only required when uploading audiences using Device IDs.\n 5. `Export Schedule`: Configure the **Frequency**, **Start Date**, **End Date**, and specific **Days of the Week** (only for **Ongoing** exports).\n 6. `Additional Fields`: Add extra fields to your export for personalization, with the option to alias the output for further customization.\n 7. `Google Specific Consents`: If you're targeting users in the EU, Google requires that you provide these consent fields as well for this destination. Otherwise Google will exclude them from your targeting.\n11. Finally, click **Export** to send the audience to **Google Ads**!\n\n> 📘\n> \n> Note\n> \n> Google Ads automatically removes users from Customer Match lists after `540` days unless the list is updated.\n\nTo view your audience, log in to **Google Ads**, click **Tools** in the left-hand sidebar, navigate to the **Audience manager** tab, and find your audience name in the table.\n\n> 👍\n> \n> Success\n> \n> You have successfully exported the audience!\n\n![](https://files.readme.io/0c39ed815d7477479d9af102014ee74358d5969912dec69d5ead6700c09f00f4-image.png)\n\n> 📘\n> \n> Note\n> \n> Experiencing issues connecting or exporting to **Google Ads**? Check out our troubleshooting [guide](https://docs.growthloop.com/docs/google-ads-troubleshooting-adding-growthloop-to-allowlist) or reach out to us at [support@growthloop.com](mailto:support@growthloop.com). We’ll get back to you shortly to help resolve the issue!\n\nUpdated 4 months ago\n\n* * *","2024-03-20T21:02:26.872Z","069d8db0-7abb-4b34-b87c-fdc3ea77f708",[],[],{"_40":888,"_128":889,"_130":890,"_132":891,"_134":-5,"_13":-5,"_120":892,"_122":136,"_25":893,"_138":-5,"_139":894,"_141":895},"How to set up Intercom as a destination | GrowthLoop Docs","how-to-set-up-intercom-as-a-destination-growthloop-docs","https://docs.growthloop.com/docs/intercom","# How to set up Intercom as a destination\n\nLearn how to setup Intercom as a destination for exports\n\nIn this Help Center article, we will walk you through the steps to get Intercom connected as a destination in the GrowthLoop web application. Once connected, you will be able to send your audience segments to Intercom for marketing activation!\n\nWhen you sign into the Segmentation Platform, navigate to the **Destinations** tab on the left sidebar and click **New Destination** in the top right corner.\n\nClick **New Destination** and scroll until you find Intercom. Intercom will be under the Livechat section. Click **Add Intercom**.\n\n![](https://files.readme.io/0eb0597-mailchimp_new_destination.png)\n\nWhen you click **Add Intercom**, you will be redirected to the Intercom login page. Once you input your login credentials, Intercom will have you authorize access to your GrowthLoop Instance.\n\n![](https://files.readme.io/c0b8064-select_intercom.png)\n\nWhen you click **Authorize Access** for Intercom, you will be redirected back to your GrowthLoop instance, where you will input the following information:\n\n![](https://files.readme.io/52db8c5-intercom_permissions.png)\n\n* **Team:** This is the team that your user belongs to in GrowthLoop software. If you have configured multiple teams in your org, be sure to select the team that your user belongs to.\n* **Destination Name:** This how the destination will be named and referred to in to the app going forward\n* **Sync Frequency:** Please select Daily or Hourly, this will control how often GrowthLoop exports audiences to Facebook\n* **OAUTH Token**: These should be automatically populated when redirected to the GrowthLoop App. If not, please ensure that you have previously generated the token for your account.\n\n![](https://files.readme.io/596597c-configure_intercom.png)\n\nCongratulations! Intercom is set up and ready for audiences!\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:27.363Z","e5516aa9-5d02-441a-ad6b-b9e5cbf369e8",[],[],{"_40":897,"_128":898,"_130":899,"_132":900,"_134":-5,"_13":-5,"_120":901,"_122":136,"_25":902,"_138":-5,"_139":903,"_141":904},"How to set up Iterable as a destination | GrowthLoop Docs","how-to-set-up-iterable-as-a-destination-growthloop-docs","https://docs.growthloop.com/docs/iterable","# How to set up Iterable as a destination\n\nLearn how to set up Iterable as a destination so you can start exporting audiences to it.\n\nThis article outlines the steps necessary to set up Iterable as a GrowthLoop destination and begin exporting audiences for activation.\n\nTo connect the GrowthLoop application to Iterable, you must have an Iterable account and create a server-side API Key. You will enter this API Key upon creating your Iterable destination.\n\n![](https://files.readme.io/fecbc56-iterable_api_key.png)\n\n1. Select **Destinations** from the left rail of your GrowthLoop home screen.\n \n ![](https://files.readme.io/6b91320-select_destinations_iterable.png)\n2. Click **New Destination** on the top right.\n \n ![](https://files.readme.io/0c76928-iterable_new_destination.png)\n3. When the **Select Destination** window pops up, type **Iterable** into the Search Bar and click **Add Iterable**.\n \n ![](https://files.readme.io/a095c9a-Screenshot_2024-06-06_at_4.44.20_PM.png)\n4. Clicking **Iterable** will require you to select/insert the following information:\n \n ![](https://files.readme.io/7bfe1f8-image.png)\n \n 1. **Destination Name:** This is how the destination will be named and referred to in the app going forward. It is helpful to make this name “marketer friendly” so everyone on your team knows it’s purpose.\n 2. **Sync frequency**: This is the default frequency your audiences will be synced to a destination. Marketers can always change the frequency of an export, but this sets the default.\n 3. **API Key**: API Key generated from your Iterable Account. To generate in Iterable, go to Integrations > API Keys, click \"New API Key\", name it, choose the Server-side option, click \"Create\", and then save the copied key securely for future use.\n5. Once all required information is provided, the **Create** button will turn blue. Click it to finalize the destination.\n \n ![](https://files.readme.io/3775c14-image.png)\n \n\n6. Navigate to the Audiences section in the left sidebar. From there, you can either select an existing audience or create a new one. (Click [here](https://docs.growthloop.com/docs/create-an-audience) to learn how!)\n \n ![](https://files.readme.io/6edf2f7-image.png)\n \n7. After selecting or creating your audience, click **Export Audience**.\n \n ![](https://files.readme.io/6b1cca1-Screen_Shot_2023-04-30_at_9.26.44_PM.png)\n8. In the **Create Export** view, search for your **Iterable** Destination and click **Select**.\n \n ![](https://files.readme.io/9289ef2-image.png)\n \n9. Then in the **Export Settings** tab, configure your desired **Campaign Type** and **Export Schedule**.\n \n ![](https://files.readme.io/3a2b308-image.png)\n \n10. Next, configure your match fields in the **Match Fields** tab. Currently, only **Email Address** is supported, with potential for more options in the future!\n \n ![](https://files.readme.io/9df3243-image.png)\n \n11. Lastly, click **Export**, and you're done! You can double check a successful export to **Iterable** by navigating to your audience viewer **Exports** tab within your GrowthLoop app to view the activity tracker and make any scheduling changes you may need.\n \n ![](https://files.readme.io/e52f6a2-iterable_pizza_tracker.png)\n12. To see your audience in **Iterable**, navigate to the Audience tab and click **Lists**.\n \n ![](https://files.readme.io/1894e50-iterable_lists.png)\n\nExperiencing any issues connecting to Iterable as a destination? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and we’ll be in touch shortly!\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:27.238Z","7748dfe3-0038-4c1e-a903-ecaafb299069",[],[],{"_40":906,"_128":907,"_130":908,"_132":909,"_134":-5,"_13":-5,"_120":910,"_122":136,"_25":911,"_138":-5,"_139":912,"_141":913},"How to set up Klaviyo as a destination | GrowthLoop Docs","how-to-set-up-klaviyo-as-a-destination-growthloop-docs","https://docs.growthloop.com/docs/klaviyo","# How to set up Klaviyo as a destination\n\nIn this Help Center article, we will walk you through the steps to get Klaviyo connected as a destination in the Growthloop web application. Once connected, you will be able to send your audience segments to Klaviyo for marketing activation!\n\n \n\n1. When you sign into the Segmentation Platform, navigate to the **Destinations** tab on the left sidebar.\n2. Click **New Destination** in the top right corner.\n3. When the **Select Destination** window pops up, scroll to find Klaviyo and click **Add Klaviyo**.\n4. Provide the following information:\n 1. **Destination Name:** This how the destination will be named and referred to in to the app going forward.\n 2. **Sync Frequency**: How frequently audiences will be synced to Klaviyo.\n 3. **API Key**: You should be able to find your API Key within Klaviyo.\n5. Click **Create**.\n\nCongratulations! You’ve successfully added Klaviyo as a destination. Now we are ready to export an audience\n\n \n\n1. Once your audience is ready, click **Export** on the top right.\n2. Search for and select **Klaviyo**.\n3. Click **Start Export**.\n\nAnd there you have it! You’ve successfully exported an audience to Klaviyo.\n\n \n\n1. Log in to **Klaviyo**.\n2. Navigate to **Lists & Segments** tab. You will see your GrowthLoop audiences kept in sync on this tab. You can now add any of these lists to Klaviyo campaigns to have messaging sent to users in the lists.\n\nExperiencing any issues connecting to Klaviyo as a destination? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and we’ll be in touch shortly!\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:27.625Z","97aed7cf-da3b-4b38-a731-5dc3f614bad2",[],[],{"_40":915,"_128":916,"_130":917,"_132":918,"_134":-5,"_13":-5,"_120":919,"_122":136,"_25":920,"_138":-5,"_139":921,"_141":922},"How to set up LinkedIn Ads as a destination | GrowthLoop Docs","how-to-set-up-linkedin-ads-as-a-destination-growthloop-docs","https://docs.growthloop.com/docs/linkedin-ads","# How to set up LinkedIn Ads as a destination\n\nLearn how to set up LinkedIn Ads as a destination so you can start exporting audiences to it.\n\nIn this Help Center article, we will walk you through the steps to get LinkedIn Ads connected as a destination in GrowthLoop. Once connected, you will be able to send your audience segments to LinkedIn Ads for marketing activation!\n\nWhen you sign into the Segmentation Platform, navigate to the **Destinations** tab on the left sidebar and click **New Destination** in the top right corner\n\n![](https://files.readme.io/15ba05b-add_linkedin_destination.png)\n\nWhen the **Select Destination** window pops up, type LinkedIn into the Search Bar to find LinkedIn Ads and click **Add LinkedIn Ads**.\n\n![](https://files.readme.io/5085efd-select_linkedin_destination.png)\n\nClicking “Add LinkedIn Ads” will take you to the LinkedIn login page. This is where you will sign in with your LinkedIn credentials. **Note:** You should use your LinkedIn account that has access to the Ads account you would like to setup as a destination.\n\n![](https://files.readme.io/41bfcd3-linkedin_oauth.png)\n\nOnce you Login, you will be routed back to the GrowthLoop web application, which will require you to select/insert the following information:\n\n* **Destination Name:** This how the destination will be named and referred to in to the app going forward. It is helpful to make this name “marketer friendly” so everyone on your team knows it’s purpose.\n* **Sync frequency**: This is the default frequency audiences will be synced to a destination. Marketers can always change frequency of an export to LinkedIn, but this sets the default.\n* **Ad Account**: This dropdown should automatically populate with Ads Accounts your LinkedIn account has access to. Select the Ads Account you would like to add as a destination. You can always add an additional destination if you’d like to add another LinkedIn Ads account in the future.\n* **Access Token**: This will automatically populate from LinkedIn.\n* **Refresh Token**: This will automatically populate from LinkedIn.\n\nGo ahead and select Create, and we’ll validate we have all the proper permissions to load audience data to LinkedIn.\n\n![](https://files.readme.io/7f31434-Screen_Shot_2023-04-27_at_10.23.24_PM.png)\n\nYou should now see LinkedIn Ads in your list of connected destinations!\n\n![](https://files.readme.io/546ce0f-linkedin_ads_list_of_destinations.png)\n\nTo build an audience and export it to LinkedIn, click **New Audience**\n\n![](https://files.readme.io/f7c24bf-linkedin_new_audience.png)\n\nIn the Builder, create your desired Audience. In this example audience, we are going to target our Customers who live in New York. Once you finish building the audience, click **Export Audience**\n\n![](https://files.readme.io/9236bd8-linkedin_export_audience.png)\n\nIn the **Create Export** view, search for your Linkedin Destination.\n\n![](https://files.readme.io/9eecf87-linkedin_export_modal.png)\n\nBefore starting the export, press the **Settings** Button to indicate if you are exporting Contacts or Companies and choose the match fields. Match fields available depend on the match type you choose, as shown below.\n\n![](https://files.readme.io/c727652-linkedin_contact_match.png) ![](https://files.readme.io/23f3dcc-linkedin_company_match.png)\n\nClick **Activate** to save these settings and you will be brought back to the Create Export view, where you can set up your desired Campaign Type and Export Schedule, and click the **Start Export** button.\n\n![](https://files.readme.io/ae66cac-linkedin_export_modal.png)\n\nAnd that’s it! You’ve successfully exported an Audience to LinkedIn Ads!\n\n![](https://files.readme.io/fd0f223-linkedin_export_scheduled.png)\n\nOnce you export an audience to the LinkedIn Ads, you can log in to your LinkedIn Ads console and see if the audience was successfully routed to LinkedIn Ads. In the top left dropdown, click **Plan** and you will see Audiences as an option in the dropdown. Here, you will find your newly exported audience in the list.\n\n![](https://files.readme.io/59a17b7-linkedin_ads_audiences.png)\n\nKeep in mind that the sync frequency and internal pipeline operations will impact how quickly your audience appears in LinkedIn Ads after being exported from the application. Note that large audiences can take longer than 48 hours to process and any audience under 300 contacts might not process.\n\nExperiencing any issues when connecting to Linkedin Ads? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and we’ll be in-touch shortly to help resolve the matter!\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:27.730Z","1bd900bb-8e46-465e-bb0a-4befd8857e1f",[],[],{"_40":924,"_128":925,"_130":926,"_132":927,"_134":-5,"_13":-5,"_120":928,"_122":136,"_25":929,"_138":-5,"_139":930,"_141":931},"How to set up MailChimp as a destination | GrowthLoop Docs","how-to-set-up-mailchimp-as-a-destination-growthloop-docs","https://docs.growthloop.com/docs/mailchimp","# How to set up MailChimp as a destination\n\nLearn how to connect Mailchimp as a Destination in GrowthLoop\n\nMailchimp is a widely-used marketing automation platform and email marketing service for managing mailing lists and creating email marketing campaigns to send to customers.\n\nIn this Help Center article, we will walk you through the steps to get Mailchimp connected as a destination in the GrowthLoop web application. Once connected, you will be able to send your audience segments to Mailchimp for marketing activation!\n\n‍\n\nTo obtain your API Key, perform the following actions:\n\n1. Navigate to the [API Key section](https://login.mailchimp.com/?referrer=%2Faccount%2Fapi%2F) of your Mailchimp account.\n2. If you already have an API Key listed and you would like to use it for the GrowthLoop application, simply copy it and save it down somewhere for quick access. Otherwise, click Create a Key and give it a descriptive name so you know which key you’ll use to connect into GrowthLoop.\n\n![](https://files.readme.io/40e5ec3-mailchimp_api_key.png)\n\nTo obtain your **List ID**, perform the following actions:\n\n1. Click the **Audience** icon in your menu bar\n2. Click **All Contacts**.\n\n![](https://files.readme.io/eabee0a-mailchimp_audience_menu.png)\n\n3. If you have more than one audience, click the Current audience drop-down and choose the audience you would like GrowthLoop to send audience segments to.\n4. Click the **Settings** drop-down and choose Audience name and defaults.\n5. In the **Audience ID** section, you’ll see a string of letters and numbers. This is your Audience ID (aka List ID). Copy this and save it somewhere for quick access.\n\n![](https://files.readme.io/994fd8d-mailchimp_list.png)\n\nOnce you have your Mailchimp API Key and List ID, open up your GrowthLoop web app and perform the following actions:\n\n1. In the lefthand menu, navigate to Destinations\n2. Click on New Destination in the top right corner to connect to a new destination for your audiences.\n\n![](https://files.readme.io/0eb0597-mailchimp_new_destination.png)\n\n3. Scroll until you find the Email section, and click on Add Mailchimp.\n\n![](https://files.readme.io/8e0b980-add_mailchimp_destination.png)\n\n4. Select the Team that will be using this destination, label the destination, and select the desired Sync Frequency. Then enter in your API Key and List ID from the actions above, and click Create once finished.\n\nThat’s it! You should now see Mailchimp as an established destination in the GrowthLoop web app. You can now segment audiences and export them to Mailchimp!\n\n**Please Note:** Mailchimp requires us to send all audience segments to the same ‘Audience’ list in Mailchimp, instead of breaking out into different lists as it typical for other email clients. To help provide visibility into which users fall into which audience segment created and exported from GrowthLoop, we will Tag the users with the name of the audience export from GrowthLoop. This should allow easy selection when attaching your creative and launching you campaign!\n\n‍\n\nExperiencing any issues when connecting to the Mailchimp destination? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and we’ll be in-touch shortly to help resolve the matter!\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:28.077Z","e9e418d4-1b8d-4a6e-8b15-2b3ad4e01947",[],[],{"_40":933,"_128":934,"_130":935,"_132":936,"_134":-5,"_13":-5,"_120":937,"_122":136,"_25":938,"_138":-5,"_139":939,"_141":940},"How to set up Marketo as a destination | GrowthLoop Docs","how-to-set-up-marketo-as-a-destination-growthloop-docs","https://docs.growthloop.com/docs/marketo","# How to set up Marketo as a destination\n\nThis article outlines the steps necessary to set up Marketo as a GrowthLoop destination. Once connected, you can begin sending audience segments to Marketo for activation!\n\nYou will need an access token in Marketo to enable connection to the GrowthLoop application. To find your access tokens or create a new one, follow the [Marketo instructions](https://developers.marketo.com/rest-api/authentication/#:~:text=The%20Client%20ID%20and%20Client,in%20the%20REST%20API%20section.&text=access_token%20%E2%80%93%20The%20token%20that%20you,authenticate%20with%20the%20target%20instance.) for Creating an Access Token. Following the steps provided will create a **Client ID** and **Client Secret**, which should be saved and written down for later use connecting to the GrowthLoop application.\n\n![](https://files.readme.io/076eca2-marketo_api.png)\n\nFollow the instructions in this [Marketo documentation](https://developers.marketo.com/rest-api/base-url/) to find the base URL for your Marketo Rest endpoint. Save this URL _without the /rest_ to be used as the instance URL when connecting to the GrowthLoop application. If you don’t remove the “/rest” part of the base URL, your connection will not work.\n\n![](https://files.readme.io/a564471-marketo_endpoint.png)\n\nSelect **Destinations** from the left rail of your GrowthLoop home screen.\n\nClick **New** **Destination** on the top right.\n\nScroll to the CRM \\***\\*section and click** Add Marketo\\*\\*.\n\n![](https://files.readme.io/03ecc7b-marketo_select_destination.png)\n\nA modal will appear to configure the connection to Marketo. Enter the required information:\n\n* **Destination Name:** A custom name for your destination.\n* **Sync Frequency:** The frequency at which GrowthLoop will export audiences to Marketo (hourly or daily).\n* **Client ID:** created when creating an access token\n* **Client Secret:** created when creating an access token\n* **Instance URL:** endpoint base URL without the “/rest”\n\n![](https://files.readme.io/08620d6-marketo_configuration.png)\n\nClick **Create** and you are set to export your first audience to Marketo! You can confirm that your Marketo account is connected by clicking **Destinations** on the left rail.\n\nExperiencing any issues connecting to Marketo as a destination? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and we’ll be in touch shortly!\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:28.228Z","68d01f2c-b35a-48e4-9834-88be72ccfe9a",[],[],{"_40":942,"_128":943,"_130":944,"_132":945,"_134":-5,"_13":-5,"_120":946,"_122":136,"_25":947,"_138":-5,"_139":948,"_141":949},"How to set up Maropost as a destination | GrowthLoop Docs","how-to-set-up-maropost-as-a-destination-growthloop-docs","https://docs.growthloop.com/docs/maropost","# How to set up Maropost as a destination\n\nLearn how to setup Maropost as a Destination for exports\n\nThis article outlines the steps necessary to set up Maropost as a GrowthLoop destination. Once connected, you can begin sending audience segments to Maropost for activation!\n\n* Maropost account ID\n* Maropost API key\n\nFor help finding your Maropost Account ID, click [here](https://galaxy.maropost.com/s/article/Managing-Accounts-and-Billing-in-Service-Cloud).\n\nFor help finding or creating a Maropost API key, click [here](https://galaxy.maropost.com/s/article/API-Keys#:~:text=The%20API%20Keys%20page%20in,Settings%20page%2C%20select%20API%20Keys.).\n\nSelect **Destinations** from the left rail of your GrowthLoop home screen.\n\nClick **New** **Destination** on the top right.\n\n![](https://files.readme.io/0eb0597-mailchimp_new_destination.png)\n\nScroll to the Email \\***\\*section and click** Add Maropost\\*\\*.\n\n![](https://files.readme.io/e529842-select_maropost.png)\n\nFill out the following **Destination** and **Credentials** fields, then click **Create.**\n\n![](https://files.readme.io/e6822fe-maropost_configuration.png)\n\n* **Destination Name:** A custom name for your destination.\n* **Sync Frequency:** The frequency at which GrowthLoop will export audiences to Maropost (hourly or daily).\n* **Account ID:** Your Maropost Account ID.\n* **API Key:** Your Maropost API Key.\n\nClick **Create** and you are set to export your first audience to Maropost! You can confirm that your Maropost account is connected by clicking **Destinations** on the left rail.\n\n![](https://files.readme.io/3681628-maropost_destination_list.png)\n\nHappy exporting!\n\nExperiencing any issues connecting to Maropost as a destination? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and we’ll be in touch shortly!\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:28.333Z","8dd1c96a-8312-4f2a-ae0f-31e4bbbcd981",[],[],{"_40":951,"_128":952,"_130":953,"_132":954,"_134":-5,"_13":-5,"_120":955,"_122":136,"_25":956,"_138":-5,"_139":957,"_141":958},"How to set up Microsoft Ads as a destination | GrowthLoop Docs","how-to-set-up-microsoft-ads-as-a-destination-growthloop-docs","https://docs.growthloop.com/docs/microsoft-ads","# How to set up Microsoft Ads as a destination\n\nLearn how to setup Microsoft Ads as a destination for exports\n\nIn this article, we'll guide you through connecting Microsoft Ads to GrowthLoop and exporting your audiences to the destination.\n\nMicrosoft Ads is a pay-per-click platform that allows you to serve ads across AOL, Yahoo, Bing, and their owned/partner sites. It’s a great complement to the suite of sites included in the Google Ads family, another popular paid media option available as a GrowthLoop destination.\n\n* Please have the following credentials ready:\n * **Username** and **password** for your company’s Microsoft Ads account.\n * **Account ID**: This can be found in the URL when you're logged into Microsoft Ads. Look for the numeric value that appears after `aid=` in the URL.\n * **Customer ID**: This is also found in the same URL, immediately following `cid=`.\n* You must manually create at least one **Customer Match** audience in the Microsoft Ads interface. During this process, you'll be prompted to agree to Microsoft’s Terms & Conditions. Once you've accepted the terms and created the audience, GrowthLoop will be able to send audiences to Microsoft Ads via the API.\n\n> 📘\n> \n> If you have these credentials on hand and have previously created a Customer Match audience, you can skip down to **Set up destination.**\n\n1. Select **Destinations** from the left rail of your GrowthLoop home screen.\n2. Click **New** **Destination** on the top right.\n3. Scroll to the **Ads** section and click **Add Microsoft Ads**.\n4. You will be redirected to a Microsoft Ads login page, where you will enter the login credentials you use to access your company’s Microsoft Ads account.\n\n> 📘\n> \n> GrowthLoop can only connect to Microsoft Ads child accounts, not manager (MCC) accounts. Please ensure you're using the correct account type when setting up the integration.\n\n5. Once you enter these credentials, you will be redirected to the GrowthLoop application. A modal window will appear asking you to enter the following information:\n 1. **Destination Name:** A custom name for your Microsoft Ads destination.\n 2. **Sync Frequency:** The frequency at which GrowthLoop will export audiences to your destination (hourly or daily).\n 3. **Access Token** \\[DO NOT EDIT\\]: GrowthLoop auto-populates this field based on the Microsoft Ads authentication performed in the previous step.\n 4. **Refresh Token** \\[DO NOT EDIT\\]: GrowthLoop auto-populates this field based on the Microsoft Ads authentication performed in the previous step.\n 5. **Customer ID:** Your Customer ID that appears after `aid=` in the URL.\n 6. **Account ID:** Your Account ID that appears after `cid=` in the URL.\n6. Click **Create** and you are set to export your first audience to Microsoft Ads! You can confirm that your Microsoft Ads account is connected by clicking **Destinations** on the left rail.\n\n7. Navigate to the **Audiences** tab in the left sidebar.\n \n8. Select an existing audience or create a new one. Need help creating an audience? Click [here](https://docs.growthloop.com/docs/create-an-audience) for a step-by-step guide.\n \n9. Once your audience is ready, click the **Export** button in the upper-right corner.\n \n10. In the export modal, search for **Microsoft Ads** and click **Select**.\n \n11. Under **Configure Match Field Settings**, map the column containing email addresses to the `Email Address (Required)` field. Then click **Next**.\n \n12. Set your export settings:\n \n * **Export Name**: Auto-filled with your audience name for easy reference in Microsoft Ads.\n * **Campaign Type**: Choose between a one-time export or an ongoing sync.\n * **Export Schedule**: Define the frequency, start and end dates, and specific days of the week (for ongoing exports).\n13. Click **Export** to send your audience to **Microsoft Ads**.\n \n\n> 📘\n> \n> GrowthLoop configures exports to Microsoft Ads so that users stay in the audience indefinitely. There's no expiration unless you manually remove them.\n\nTo find an exported audience in Microsoft Ads, navigate to **Tools > Audiences.** Your audience will land here as a **Customer Match List.**\n\n> 👍\n> \n> You have successfully exported the audience!\n\n![](https://files.readme.io/e8887cb-microsoft_ads_audiences.png)\n\n> 📘\n> \n> Experiencing any issues connecting to Microsoft Ads as a destination? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and we’ll be in touch shortly!\n\nUpdated 4 months ago\n\n* * *","2024-03-20T21:02:28.539Z","a0950f70-f0f5-431c-82d4-89d996675629",[],[],{"_40":960,"_128":961,"_130":962,"_132":963,"_134":-5,"_13":-5,"_120":964,"_122":136,"_25":965,"_138":-5,"_139":966,"_141":967},"How to set up Pinterest as a destination | GrowthLoop Docs","how-to-set-up-pinterest-as-a-destination-growthloop-docs","https://docs.growthloop.com/docs/pinterest-destination","# How to set up Pinterest as a destination\n\nIn this Help Center article, we will walk you through the steps to get **Pinterest Ads** connected as a destination in the GrowthLoop web application. Once connected, you will be able to send your audience segments to Pinterest Ads for marketing activation!\n\nWhen you sign into the GrowthLoop, navigate to the **Destinations** tab on the left sidebar and click **New Destination** in the top right corner\n\n![](https://files.readme.io/ce47a8e-Screenshot_2024-01-25_at_11.24.20_AM.png)\n\nWhen the **Select Destination** window pops up, scroll to find Pinterest or Type in the search box and click **Add**.\n\n![](https://files.readme.io/44e5ce1-Screenshot_2024-02-08_at_3.11.08_PM.png)\n\nClicking “Add Pinterest” will take you to the Pinterest login page. This is where you will sign in with your **Pinterest Ads Manager credentials**.\n\n![](https://files.readme.io/aab86f1-Screenshot_2024-01-25_at_11.26.32_AM.png)\n\nOnce you click login, it will ask if you’d like to **Authorize** Pinterest to your GrowthLoop subscription. Click Continue.\n\n![](https://files.readme.io/a7084b0-Screenshot_2024-01-25_at_11.54.23_AM.png)\n\nYou’ll be routed back to the GrowthLoop web application, which will require you to select/insert the following information\n\n* **Destination Name:** This is how the destination will be named and referred to in to the app going forward\n* **Sync frequency**: how frequently audiences will be synced to the destination\n* **Ad account ID**: In the Pinterest UI, log in and click the dropdown in the top left. Click **Ad accounts** and copy the Ad account ID and paste it in this field.\n* **Access token:** this will automatically populate when you initially log into your Pinterest Ads Manager console via the GrowthLoop application\n* **Refresh Token**: this will automatically populate when you initially log into your Pinterest Ads Manager console via the GrowthLoop application\n\nYou should now see Pinterest in your list of connected destinations!\n\n![](https://files.readme.io/1da7d42-Screenshot_2024-01-25_at_11.55.13_AM.png)\n\nNow let’s **export an audience** to Pinterest. Click on Audiences in the left side bar, and choose the audience you’d like to export.\n\nClick the **Export Audience** button in the top right, and select Pinterest. You’ll be prompted next to configure **match field settings.**\n\n![](https://files.readme.io/e24676d-Screenshot_2024-01-26_at_12.46.19_PM.png) ![](https://files.readme.io/9621eef-Screenshot_2024-02-08_at_3.08.41_PM.png)\n\nClick Select and proceed. You’ll next want to configure the Match Field(s) and Export Settings. For this instance with Pinterest the only available Match Field is email, these will need to be 1:1 so from the drop down you’ll want to select email.\n\n![](https://files.readme.io/5ce9872-Screenshot_2024-02-01_at_5.24.15_PM.png)\n\nNext let’s define **Export Settings.**\n\n* **Export Name:** Give a name to your export for easy reference.\n* **Campaign Type:** Choose between Ongoing (continuous campaign with no end date) and One Time (for a single export).\n* **Frequency:** Decide how often you want to update audience membership and send it to Pinterest. Options include Every Fifteen Minutes, Thirty Minutes, Hourly, Daily, Weekly, and Monthly.\n* **Start:** The default is to start Now, but you can choose a specific time from the dropdown.\n* **End:** The default is to end Never, but you can choose a specific time from the dropdown if needed.\n\n![](https://files.readme.io/bef5352-Screenshot_2024-02-01_at_5.02.26_PM.png)\n\nClick **Export** and you’ll see Active Export in Green to verify export is live.\n\n![](https://files.readme.io/4788bf4-Screenshot_2024-02-01_at_5.22.20_PM.png)\n\nOnce you’ve exported an audience to Pinterest, you can log in to your Pinterest Ads manager and see if the audience successfully routed to Pinterest. In the top left dropdown, click **Audiences** and under Business column click Audiences again and you will find your newly exported audience here.\n\nKeep in mind that the sync frequency and internal pipeline operations will impact how quickly your audience appears in Pinterest Ads Manager after being exported from the application.\n\n![](https://files.readme.io/a40775c-Screenshot_2024-01-25_at_11.57.47_AM.png)\n\n**Congratulations! You’ve now successfully connected Pinterest as a destination, and set up an active audience export within GrowthLoop!**\n\nExperiencing any issues when connecting to Attentive? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and we’ll be in-touch shortly to help resolve the matter!\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:28.810Z","24e4a6a7-ce2c-4e7c-adff-c97359e0c6af",[],[],{"_40":969,"_128":970,"_130":971,"_132":972,"_134":-5,"_13":-5,"_120":973,"_122":136,"_25":974,"_138":-5,"_139":975,"_141":976},"How to set up Sailthru as a destination | GrowthLoop Docs","how-to-set-up-sailthru-as-a-destination-growthloop-docs","https://docs.growthloop.com/docs/sailthru","# How to set up Sailthru as a destination\n\nIn this Help Center article, we will walk you through the steps to get **Sailthru** connected as a destination in the GrowthLoop web application. Once connected, you will be able to send your audience segments to it for marketing activation!\n\n1. Navigate to the **Destinations** tab on the left sidebar and click **New Destination** in the top right corner.\n \n ![](https://files.readme.io/a23e2c8-Untitled.png)\n2. When the **Select Destination** window pops up, type **Sailthru** into the Search Bar and click **Add Sailthru**.\n \n ![](https://files.readme.io/c4c5f30-image.png)\n \n3. Clicking **Sailthru** will require you to select/insert the following information:\n \n 1. **Destination Name:** This is how the destination will be named and referred to in the app going forward. It is helpful to make this name “marketer friendly” so everyone on your team knows it’s purpose.\n 2. **Sync frequency**: This is the default frequency your audiences will be synced to a destination. Marketers can always change the frequency of an export, but this sets the default.\n 3. **API Key** and **API Secret**: To retrieve these two parameters, login to your [Sailthru](https://my.sailthru.com/) account, navigate to the [API Postbacks](https://my.sailthru.com/settings/api_postbacks) page, and click on the lock icon next to \"API Key and Secret\". Once revealed, copy and paste them into the designated fields.\n4. Once all required information is provided, the **Create** button will turn blue. Click it to finalize the destination.\n \n ![](https://files.readme.io/0fbec69-image.png)\n \n\n5. Navigate to the Audiences section in the left sidebar. From there, you can either select an existing audience or create a new one. (Click [here](https://docs.growthloop.com/docs/create-an-audience) to learn how!)\n \n ![](https://files.readme.io/6edf2f7-image.png)\n \n6. After selecting or creating your audience, click **Export Audience**.\n \n ![](https://files.readme.io/6b1cca1-Screen_Shot_2023-04-30_at_9.26.44_PM.png)\n7. In the **Create Export** view, search for your **Sailthru** Destination and click **Select**.\n \n ![](https://files.readme.io/967d84f-image.png)\n \n8. Next, navigate to the **Export Settings** tab and configure your preferred **Campaign Type**, **API to Use**, and **Export Schedule**. Please note: We recommend using the Jobs API for exporting audiences. However, if you intend to use triggered messages in Sailthru, please select the Users API instead.\n \n ![](https://files.readme.io/8915e31-image.png)\n \n9. Next, configure your match fields in the **Match Fields** tab. Currently, only **Email Address** is supported, with potential for more options in the future!\n \n ![](https://files.readme.io/cc71955-image.png)\n \n10. Finally, click **Export**, and you're all set! Congratulations on successfully exporting your audience to Sailthru. Please note: Your audience will appear in Sailthru as a \"Primary List,\" which is crucial for organizing subscriber data and sending campaigns. Sailthru restricts you to a maximum of 100 Primary Lists. If you exceed this limit, your audience won't export. To manage your lists, log in to Sailthru, navigate to the Lists section, and either toggle off the Primary status or click the trash icon to delete unused lists.\n \n11. To view your audience in Sailthru, login to your [account](https://my.sailthru.com/) and navigate to the **Lists** page.\n \n\n![](https://files.readme.io/1dae05b-image.png)\n\nExperiencing any issues connecting to Sailthru as a destination? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and we’ll be in touch shortly!\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:29.146Z","7711f4d8-f4c2-4afb-af2b-0bc657056433",[],[],{"_40":978,"_128":979,"_130":980,"_132":981,"_134":-5,"_13":-5,"_120":982,"_122":136,"_25":983,"_138":-5,"_139":984,"_141":985},"How to set up Snapchat as a destination | GrowthLoop Docs","how-to-set-up-snapchat-as-a-destination-growthloop-docs","https://docs.growthloop.com/docs/snapchat","# How to set up Snapchat as a destination\n\nLearn how to connect and send audiences to Snapchat\n\nIn this article, we'll guide you through connecting Snapchat to GrowthLoop and exporting your audiences to the destination.\n\nSnapchat Ads is a digital advertising platform that allows businesses to create and run targeted, interactive, and visually engaging ads within the Snapchat app to reach its user base.\n\n1. Log into **GrowthLoop** and click the **Destinations** tab on the left sidebar.\n \n2. Then click **New Destinations** on the upper right side.\n \n3. Next, search for **Snapchat** in the destination modal and click **Add Snapchat**.\n \n4. You will be routed to the Snapchat login page - sign in with your Snapchat Ads Manager credentials.\n \n5. After signing in, click **Continue** to be routed back to GrowthLoop, where you can select and insert the required information.\n \n6. Finally, enter the necessary details in the modal and click **Create** to complete the connection.\n \n 1. `Destination Name`: Enter the name you want to give the destination.\n 2. `Sync Frequency`: Select a default export frequency to the destination.\n 3. `Ad account`: Select the ad account from the drop-down menu where you want to export your audiences.\n 4. `Refresh Token`: This will automatically populate when you initially log into your Snapchat Ads Manager console via the GrowthLoop application\n\n> 👍\n> \n> You should now see **Snapchat** in your list of connected destinations!\n\n5. Navigate to your list of audiences by clicking the **Audiences** tab on the left sidebar.\n6. Choose an existing audience or create a new one. Need help creating? Click [here](https://docs.growthloop.com/docs/create-an-audience) to learn how!\n7. Once created, click the **Export** button on the upper right side.\n8. Search for **Snapchat** in the export modal and then click **Add Snapchat**.\n9. In **Configure Match Field Settings**, click the drop-down and select one of the available match identifiers. Options include:\n 1. `Mobile Device ID`: IDFA or Google Advertising ID\n 2. `Phone`: Please include country code in phone numbers (e.g., +1 800-555-1111)\n 3. `Email`\n10. Click the **Select values** drop-down, choose the corresponding field from your dataset that contains the selected identifier, and then click **Next** to proceed.\n11. Now, set up your export settings:\n 1. `Export Name`: Automatically populated with your audience name for easy identification in the destination.\n 2. `Campaign Type`: Choose between **One Time** to export the audience once or **Ongoing** to continuously export new audience members as they qualify.\n 3. `Export Inclusion Criteria`: Choose between **All audience members** to export the full audience or **Newly added audience members** to export only those who have been added since the last export.\n 4. `Export Schedule`: Configure the **Frequency**, **Start Date**, **End Date**, and specific **Days of the Week** (only for **Ongoing** exports).\n 5. `Additional Fields`: Add extra fields to your export for personalization, with the option to alias the output for further customization.\n12. Finally, click **Export** to send the audience to Snapchat!\n\n> 👍\n> \n> You have successfully exported the audience to **Snapchat**! Please note: an audience needs at least 1,000 users to be targeted.\n\nTo view your audience, log in to **Snapchat Ads Manager**, click the **top left drop-down**, and select **Audiences**. Your newly exported audience will appear in the list.\n\n![](https://files.readme.io/ba16fd9-snapchat_audience_list.png)\n\n> 📘\n> \n> Having trouble connecting or exporting to **Snapchat**? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com), and we’ll be in touch shortly to help resolve the issue!\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:29.919Z","1c05da31-0e6a-4729-be53-2ee4fdc4ce30",[],[],{"_40":987,"_128":988,"_130":989,"_132":990,"_134":-5,"_13":-5,"_120":991,"_122":136,"_25":992,"_138":-5,"_139":993,"_141":994},"How to set up Snapchat conversions | GrowthLoop Docs","how-to-set-up-snapchat-conversions-growthloop-docs","https://docs.growthloop.com/docs/snapchat-conversions","# How to set up Snapchat conversions\n\nLearn how to create Syncs for Snapchat conversions\n\nIn this guide, we’ll walk you through syncing web, app, and offline event data from your data warehouse into Snapchat to optimize future campaigns. Let's get started!\n\nGrowthLoop enables syncing for the following Snapchat conversion events:\n\n| Event | Description | Sync Modes | Field Mappings (Required) | Field Mappings (Optional) |\n| --- | --- | --- | --- | --- |\n| `Web` | Sync and track website behaviors, such as clicks, page views, or interactions | Insert (adds new events) | `Event name`: The event’s name, such as \"Page View\" or \"Add to Cart\"

`Event Time`: When the event occurred

`Source URL`: URL of the webpage where the event took place

`Action Source`: Whether an event originated from a website, app, or offline source

`User Data`: At least one piece of user data for matching, like hashed email, phone number, etc | See full list of conversion parameters [here](https://marketingapi.snapchat.com/docs/conversion.html#conversion-parameters) |\n| `Purchase` | Sync and track when users complete a transaction on your website or within your app | Insert (adds new events) | All `Web Event` fields, plus the following:

`Currency`: The currency code of the transaction (e.g., \"USD\")

`Value`: The monetary value of the purchase | See full list of conversion parameters [here](https://marketingapi.snapchat.com/docs/conversion.html#conversion-parameters) |\n| `App` | Sync and track in-app behaviors, such as installs, opens, or interactions | Insert (adds new events) | All `Web Event` fields, plus the following:

`Mobile Ad ID`: Unique identifier, like IDFA or AAID, to deduplicate mobile events

`App ID`: Unique identifier for the app

`Extended Information`: Additional metadata about the event, such as device information and app version

`Is Advertiser Tracking Enabled?`: Whether the advertiser has user consent for tracking in compliance with privacy regulations | See full list of conversion parameters [here](https://marketingapi.snapchat.com/docs/conversion.html#conversion-parameters) |\n\n* Have a **Snapchat Ads Manager** account. Create one [here](https://forbusiness.snapchat.com/)!\n* Created a **Conversion API Key**. Navigate to the \"Events Manager\" section of Snapchat Ads Manager to generate and manage your API keys.\n* Located your **Pixel ID** for web and offline events. You can find it in the \"Events Manager\" section, within the settings for your pixel.\n* Located your **Snap App ID** for app events. Available in the \"App Ads\" section of Snapchat Ads Manager.\n\n1. Log in to **GrowthLoop** and click **Destinations** on the left sidebar.\n2. Click **New Destination** in the top right corner.\n3. Search for \"Snapchat Conversions\" and click **Add Snapchat Conversions**.\n4. Enter the required information in the modal, then click **Create**.\n 1. **Destination Name**: This is how the destination will be named and referred to in the app going forward.\n 2. **Sync Frequency**: This indicates how frequently audiences will be synced to the destination.\n 3. **Conversion API Key**: A unique key provided by Snapchat for server-to-server data sharing. Located in the Snapchat Ads Manager under the \"Events Manager\" section, where you can generate and manage API keys.\n 4. **Pixel ID**: A unique identifier for your specific Snapchat Pixel. Found in the \"Events Manager\" section of Snapchat Ads Manager, within the settings for your pixel.\n 5. **App ID**: A unique identifier for your mobile application. Available in the \"App Ads\" section of Snapchat Ads Manager, where you can manage and track app-related campaigns.\n\n5. Click **Destinations** on the left sidebar.\n6. Select **Syncs** from the options listed on the left sidebar.\n7. Then click **Create Sync** on the upper right side.\n8. Next, configure your sync by filling out the following fields:\n 1. Route Name:\n 1. **Name:** A friendly name for the sync.\n 2. **Sync frequency**: The default frequency for syncing data to the destination. The options are: **15 minutes**, **30 minutes**, **hourly**, and **daily**.\n 3. **Update Rule:** The default operation for syncing data to the destination. Snapchat supports only the **Insert** rule, which means new data is added to the destination without updating or overwriting existing data.\n 2. Source:\n 1. **Dataset/Table:** The table that holds the data you want to sync to the destination. Usually, it's organized within a user or events table.\n 2. **Dataset Unique Field(s):** The unique field(s) on the table. They will populate automatically after selecting the Dataset/Table.\n 3. **Match Field**: The column in your source table that is used to match data to the destination. Please select your email field.\n 3. Destination:\n 1. **Connection:** The destination you will sync data to. Please select **Snapchat Conversions**.\n 2. **Object Type:** Select the type of object you want to send data to. Please choose **Conversions**.\n 3. **Match Field:** Select **Email Address**, which corresponds to the email field in your source dataset.\n9. Once you finish selecting/inserting the required fields, click **Save Route**.\n10. Next, set up the field mappings to start your sync. The fields you need to map depend on the type of event:\n 1. **Web events**: Map **Event Name**, **Event Time**, **Source URL**, **Action Source**, and at least one user identifier like **Email**.\n 2. **Purchase events**: Include **Currency** and **Value** along with the web event fields.\n 3. **App events**: Map **Mobile Advertising ID**, **App ID**, **Extended Information**, and **Is Advertiser Tracking Enabled?** along with the web event fields.\n11. For Web Events, start by selecting the field from your **Source** table that has your conversion event names (e.g., PURCHASE, SAVE, START\\_CHECKOUT). In the **Destination** section, choose **Event Name** from the drop-down menu, unless it’s already selected.\n12. Next, map **Event Time**. Select the field from your **Source** table that shows the event time. Ensure the values are in Epoch/Unix format. In the **Destination** section, choose **Conversion Event Time** from the drop-down menu, unless it’s already selected.\n13. Map **Source URL**. Choose the field from your **Source** table that captures the URL of the web page where the event happened. Make sure it includes the protocol (e.g., http, https). In the **Destination** section, select **Conversion Source URL** from the drop-down menu, unless it’s already selected.\n14. Map **Action Source**. Choose the field from your **Source** table that indicates where the event took place. It must be **WEB**, **OFFLINE**, or **MOBILE\\_APP**. In the **Destination** section, select **Conversion Action Source** from the drop-down menu, unless it’s already selected.\n15. Lastly, map a user identifier, such as **Email**. Choose the field from your **Source** table that contains the **Email Address**. In the **Destination** section, select **Email Address** from the drop-down menu, unless it’s already selected.\n16. Click **Update Route**, then return to your sync and enable it by clicking the toggle at the top of the page!\n\n> 👍\n> \n> You’ve successfully created a conversion sync to Snapchat. You should see it in the Syncs table.\n\nTo confirm your web event data is received, log in to your **Ads Manager** account, select the drop-down in the upper left corner, and choose **Events Manager**. There, you’ll see your recently uploaded conversion events!\n\n![](https://files.readme.io/7e62ce8-image.png)\n\n> 📘\n> \n> If you experience any issues when connecting to or creating syncs to Snapchat Conversions, please reach out to us at [support@growthloop.com](mailto:support@growthloop.com), and we’ll be in touch shortly to help resolve the matter!\n\nUpdated 5 months ago\n\n* * *","2025-06-20T22:58:03.206Z","1ba21286-1ef6-476d-a2f7-bdc825d4fd53",[],[],{"_40":996,"_128":997,"_130":998,"_132":999,"_134":-5,"_13":-5,"_120":1000,"_122":136,"_25":1001,"_138":-5,"_139":1002,"_141":1003},"How to set up Snowflake as a destination | GrowthLoop Docs","how-to-set-up-snowflake-as-a-destination-growthloop-docs","https://docs.growthloop.com/docs/snowflake-destination","# How to set up Snowflake as a destination\n\nThis article outlines the steps necessary to set up Snowflake as a GrowthLoop destination and begin exporting audiences for activation.\n\n* Snowflake warehouse, database, schema, and table names\n* Snowflake account ID\n* Snowflake username, role, passphrase, and private key\n\nIf you already have these credentials on hand, you can skip down to **Setting Snowflake as a Destination.**\n\nWhen you’ve identified where you want GrowthLoop to deposit audience data in your data warehouse, you can confirm the names of your warehouse, database, and schema by clicking anywhere on the bar to the upper left of your query editor and generating a dropdown with this information.\n\n![](https://files.readme.io/aa79c9d-Untitled.png)\n\nLog into your Snowflake instance. The phrase below your username on the top left corner is your role.\n\n![](https://files.readme.io/eeb36a1-Untitled_1.png)\n\nClick on the dropdown arrow next to your username. The alphanumeric ID below **Log Out** is your **Account ID** (I have grayed out part of ours for security reasons).\n\n![](https://files.readme.io/8ba898c-Untitled_2.png)\n\nSelect **Destinations** from the left rail of your GrowthLoop home screen.\n\n![](https://files.readme.io/1afe5ec-Untitled_4.png)\n\nClick **New** **Destination** on the top right.\n\n![](https://files.readme.io/a7fdb0c-Untitled_3.png)\n\nScroll down to the **Data Warehouse** section and click **Add Snowflake**.\n\n![](https://files.readme.io/43869cf-Untitled_4.png)\n\nA modal window will prompt you to fill out **Destination Info** and **Credentials**.\n\n**Destination Name:** A custom name for your destination.\n\n**Sync Frequency:** The frequency at which GrowthLoop will export audiences to your destination (hourly or daily)\n\n**Table Name:** A name for the table GrowthLoop will be created in Snowflake.\n\n**Schema:** The Snowflake schema where your new table should live.\n\n**Database:** The Snowflake database where this schema lives.\n\n**Warehouse:** The Snowflake warehouse where this database lives.\n\n**Account:** Your Snowflake account ID.\n\n**Username:** The username you use to log in to Snowflake.\n\n**Role:** The role you have been assigned within Snowflake.\n\n**Passphrase:** The password you use to log in to Snowflake.\n\n**Private Key:** The private key you created in the requirements section\n\n**Columns to Export:** Columns will be exported by default when you export an audience to this Snowflake destination. Use the column names of the underlying datasets in your data warehouse. If you do not specify any column names, all columns will be exported by default.\n\nClick **Create**, and you are set to export your first audience to Snowflake! You can confirm that your Snowflake instance is connected by clicking **Destinations** on the left rail.\n\nHappy exporting!\n\nExperiencing any issues connecting to Snowflake as a destination? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and we’ll be in touch shortly!\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:30.038Z","220d342e-7f9c-4f9f-88a7-606b513b3e91",[],[],{"_40":1005,"_128":1006,"_130":1007,"_132":1008,"_134":-5,"_13":-5,"_120":1009,"_122":136,"_25":1010,"_138":-5,"_139":1011,"_141":1012},"How to set up StackAdapt as a destination | GrowthLoop Docs","how-to-set-up-stackadapt-as-a-destination-growthloop-docs","https://docs.growthloop.com/docs/stackadapt-destination","# How to set up StackAdapt as a destination\n\nIn this Help Center article, we will walk you through the steps to get StackAdapt connected as a destination in the GrowthLoop web application. Once connected, you will be able to send your audience segments to StackAdapt for marketing activation!\n\nStackAdapt is a digital advertising platform that specializes in native, display, video, connected TV, audio, in-game, and DOOH advertising.\n\n1. When you sign into GrowthLoop, navigate to the **Destinations** tab on the left sidebar and click **New Destination** in the top right corner\n2. When the **Select Destination** window pops up, scroll to find **StackAdapt** or type in the search box and click **Add**.\n3. Clicking **Add StackAdapt** will open this configuration window.\n4. Once you’ve received the **GQL API Key**, enter it along with a Destination Name and a Sync Frequency and click create.\n 1. **Destination Name:** This is how the destination will be named and referred to in to the app going forward\n 2. **Sync frequency**: how frequently audiences will be synced to the destination. The options here will be Hourly / Daily syncs.\n 3. **GraphQL API Key -** If you don’t already have it, you’ll need to reach out directly to your StackAdapt Account Manger.\n\n> 👍\n> \n> You should now see StackAdapt in your list of connected destinations!\n\n> 📘\n> \n> StackAdapt only supports adding users to a CRM audience via their API. At this time, it's not possible to remove users from an audience once they've been added.\n\n1. Now let’s export an Audience. Either create a [new one](https://docs.growthloop.com/docs/create-an-audience), or select an existing one by navigating to the **Audience** tab in the left sidebar.\n2. Select the Audience you’d like and then click **Export audience** button in the top right.\n3. Scroll to find **StackAdapt** or type in the search box and click **Select.**\n4. Next let’s configure **Export Settings**. Start with giving an **Export Name**, and then define the **Campaign Type** as ongoing or one time.\n 1. **Frequency:** how frequently the audience will be synced to the destination. Options are one time or every Fifteen Minutes, Thirty Minutes, Hourly, Daily, Weekly, or Monthly.\n 2. **When should sync end?** An export can stay active forever, or be scheduled a specific end date.\n5. Now let’s configure **Match Fields**. With StackAdapt the only option is email. Use the drop down to select.\n6. Once you’ve configured the above settings, click the **Blue Export Button** on the bottom right.\n7. After you’ve exported the selected audience to **StackAdapt**, you can view this audience in **StackAdapt** by logging into your account.\n8. You’ll be able to view the exported audiences in **two places**.\n 1. You can directly click into the **Audiences tab** from the main dashboard or navigation menu to view a list of all Audiences.\n 2. The other option is when setting up a StackAdapt Campaign you’ll be prompted to select a target audience and should see your newly exported audience available, along with all the others.\n\n> 👍\n> \n> Congrats on setting up StackAdapt as a destination, and successfully exporting an audience!\n\n> 📘\n> \n> Experiencing any issues when connecting and/or exporting to **StackAdapt**? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and we’ll be in touch shortly to help resolve the matter!\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:30.160Z","acd3b064-3dbd-4614-80ec-2cb2901df305",[],[],{"_40":1014,"_128":1015,"_130":1016,"_132":1017,"_134":-5,"_13":-5,"_120":1018,"_122":136,"_25":1019,"_138":-5,"_139":1020,"_141":1021},"How to set up Taboola as a destination | GrowthLoop Docs","how-to-set-up-taboola-as-a-destination-growthloop-docs","https://docs.growthloop.com/docs/taboola","# How to set up Taboola as a destination\n\nLearn how to connect and send audiences to Taboola\n\nIn this article, we'll guide you through connecting Taboola to GrowthLoop and exporting your audiences to the destination.\n\n* Make sure you have a Taboola account. If not, you can create one [here](https://authentication.taboola.com/authentication/j_spring_security_check)!\n* Have your **Backstage API** credentials ready (Account ID, Client ID, and Client Secret.) If you don’t have them, contact your Account Representative.\n\n1. Log into **GrowthLoop** and click the **Destinations** tab on the left sidebar.\n \n2. Then click **New Destinations** on the upper right side.\n \n3. Next, search for **Taboola** in the destination modal and click **Add Taboola**.\n \n4. Enter the required information in the modal, then click **Create**.\n \n 1. **Destination Name**: This is how the destination will be named and referred to in the app going forward.\n 2. **Sync Frequency**: This indicates how frequently audiences will be synced to the destination.\n 3. **Account ID**: Your account identifier. Contact your Account Representative for this.\n 4. **Client ID**: The identifier to access the Backstage API. Contact your Account Representative for this.\n 5. **Client Secret**: The secret string for authenticating your account. Contact your Account Representative for this.\n\n5. Navigate to your list of audiences by clicking the **Audiences** tab on the left sidebar.\n6. Choose an existing audience or create a new one. Need help creating? Click [here](https://docs.growthloop.com/docs/create-an-audience) to learn how!\n7. Once created, click the **Export** button on the upper right side.\n8. Search for **Taboola** in the export modal and then click **Add Taboola**.\n9. Map either **Email**, **Device ID**, or both under Configure Match Field Settings. Taboola uses these fields to match customers in their system. Click **Next**.\n10. Configure your export settings:\n * **Export Name**: Automatically populated with your audience name for easy identification in the destination.\n * **Campaign Type**: Choose between a one-time export or ongoing basis.\n * **List Status**: Choose between new or existing.\n * For new lists, it will use the audience name and add records to it.\n * For existing lists, input the List ID to add records to it.\n * **Export Schedule**: Set the frequency, start date, end date, and specific days of the week.\n11. Lastly, click **Export**. Congrats on successfully exporting an audience to Taboola! To view your audience, log in to your account, click the **Audiences** tab, and select **Custom Audiences**. Note: it can take up to 1-3 days for the audience to fully populate.\n\n![](https://files.readme.io/765375f-image.png)\n\n> 📘\n> \n> Experiencing any issues when connecting and/or exporting to **Taboola**? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and we’ll be in touch shortly to help resolve the matter!\n\nUpdated 5 months ago\n\n* * *","2025-06-20T22:59:03.661Z","e56ca753-acc7-43fa-b7e7-d4b60ecc2eae",[],[],{"_40":1023,"_128":1024,"_130":1025,"_132":1026,"_134":-5,"_13":-5,"_120":1027,"_122":136,"_25":1028,"_138":-5,"_139":1029,"_141":1030},"How to set up Twitter as a destination | GrowthLoop Docs","how-to-set-up-twitter-as-a-destination-growthloop-docs","https://docs.growthloop.com/docs/twitter","# How to set up Twitter as a destination\n\nIn this Help Center article, we will walk you through the steps to get Twitter Ads connected as a destination in the GrowthLoop web application. Once connected, you will be able to send your audience segments to Twitter for marketing activation!\n\nWhen you sign into the Segmentation Platform, navigate to the **Destinations** tab on the left sidebar and click **New Destination** in the top right corner\n\n![](https://files.readme.io/9a7e74e-Untitled.png)\n\nWhen the **Select Destination** window pops up, scroll to find Twitter and click **Add Twitter**.\n\n![](https://files.readme.io/7a3655e-Untitled.png)\n\nLog in to Twitter with the account associated with your Twitter Ads Manager\n\n![](https://files.readme.io/d5abdee-Untitled_1.png)\n\nAfter authenticating with your Twitter credentials, you’ll be redirected to this screen:\n\n* **Team:** This is the team that your user belongs to in GrowthLoop software. If you have configured multiple teams in your org, be sure to select the team that your user belongs to.\n* **Destination Name:** This is how the destination will be named and referred to in the app going forward\n* **Sync Frequency:** Please select Daily or Hourly; this will control how often GrowthLoop exports audiences to Facebook\n* **Select Ad Account:** If you have multiple Ad Accounts, be sure to select the correct Account where GrowthLoop will export audiences\n* **Token & Token Secret:** These should be automatically populated when redirected to the GrowthLoop App. If not, please ensure that you have previously generated the token and secret for your account.\n\n![](https://files.readme.io/b04284e-Untitled_2.png)\n\nClick **Create**, and you are set to export your first audience to Twitter!\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:31.013Z","947d8b21-cfde-4a6b-aa76-db79d035aad6",[],[],{"_40":1032,"_128":1033,"_130":1034,"_132":1035,"_134":-5,"_13":-5,"_120":1036,"_122":136,"_25":1037,"_138":-5,"_139":1038,"_141":1039},"How to set up your data storage bucket | GrowthLoop Docs","how-to-set-up-your-data-storage-bucket-growthloop-docs","https://docs.growthloop.com/docs/bring-your-own-bucket","# How to set up your data storage bucket\n\n## Export Storage: Bring your own Bucket\n\nLearn how to leverage your own storage buckets for exports.\n\nThe GrowthLoop platform stores some data in storage buckets to route data to the marketing platform or power other features like debug logs. Your team has control over whether you choose to use a GrowthLoop-managed storage bucket or bring your bucket (BYOB).\n\nGrowthLoop only temporarily stages audience or segment membership into a staging storage bucket to allow our export service to sync the members to various marketing platforms. After routing this data is deleted, and these buckets also have a TTL of 7 days.\n\nYour team can decide to store all at-rest data in a private bucket managed within your own GCP/AWS infrastructure. Currently, we support both:\n\n* S3 (AWS)\n* Google Cloud Storage (GCS)\n\nTo setup S3 as your storage bucket follow these steps:\n\n* Create a new S3 bucket in your AWS account\n \n * Make sure to block public access\n * Setup a TTL time of your choice to enhance security\n* Create a new IAM Policy to give permissions to bucket.\n \n * In AWS, select IAM\n * Select Policies\n * Select Create Policy\n * For policy editor, select JSON\n * Copy and paste the text below into the policy editor.\n \n ```\n {\n \t\"Version\": \"2012-10-17\",\n \t\"Statement\": [\n \t\t{\n \t\t\t\"Effect\": \"Allow\",\n \t\t\t\"Action\": [\n \t\t\t\t\"s3:PutObject\",\n \t\t\t\t\"s3:GetObject\",\n \t\t\t\t\"s3:GetObjectVersion\"\n \t\t\t],\n \t\t\t\"Resource\": \"arn:aws:s3:::byob-docs-test/exports/*\"\n \t\t},\n \t\t{\n \t\t\t\"Effect\": \"Allow\",\n \t\t\t\"Action\": [\n \t\t\t\t\"s3:ListBucket\",\n \t\t\t\t\"s3:GetBucketLocation\"\n \t\t\t],\n \t\t\t\"Resource\": \"arn:aws:s3:::\",\n \t\t\t\"Condition\": {\n \t\t\t\t\"StringLike\": {\n \t\t\t\t\t\"s3:prefix\": [\n \t\t\t\t\t\t\"exports/*\"\n \t\t\t\t\t]\n \t\t\t\t}\n \t\t\t}\n \t\t}\n \t]\n }\n ```\n \n * These are the permissions you are providing in this policy.\n \n | Permission | Details |\n | --- | --- |\n | s3:PutObject | Permission to unload files to bucket |\n | s3:GetObject | Permission to retrieve objects |\n | s3:GetObjectVersion | Permission to access a specific version of an object |\n | s3:ListBucket | Permission to list some or all objects |\n | s3:GetBucketLocation | Permission to retrieve region bucket is in |\n \n * Enter a policy name and click Create Policy.\n * Assign your new IAM Policy to your GrowthLoop IAM user.\n* Create an IAM role in AWS.\n \n * Select IAM in Management Console\n * Select Roles\n * Select Create Role\n * Select AWS account and leave \"This Account\" selected for now\n * Also ensure require external ID is selected and enter placeholder 0000\n * Enter Role details and select Policy created above.\n * Enter Role Name and Description and select Create Role\n\nYou have now created an IAM policy for a bucket, created an IAM role, and attached the policy to the role.\n\nOn the role summary page, locate and record the Role ARN value.\n\n* **Additional Steps For Snowflake Integration:**\n \n * Create **Storage Integration** in Snowflake. A storage integration is a Snowflake object that stores a generated identity and access management (IAM) user for your S3 cloud storage, along with an optional set of allowed or blocked storage locations (i.e. buckets).\n \n * Run the following SQL Command in Snowflake:\n \n ```\n USE ROLE ACCOUNTADMIN;\n \n create storage integration FLYWHEEL_APP_AWS\n \n type = external_stage\n \n storage_provider = 'S3'\n \n enabled = true\n \n storage_AWS_role_arn = ''\n \n storage_allowed_locations = ('s3:///exports/');\n \n GRANT USAGE ON integration FLYWHEEL_APP_AWS to ROLE ;\n ```\n \n * Where:\n * **iam\\_role** is the Amazon Resource Name (ARN) of the IAM role you created above.\n * **bucket** is the name of a S3 bucket that stores your data files (e.g. mybucket). The required STORAGE\\_ALLOWED\\_LOCATIONS parameter and optional STORAGE\\_BLOCKED\\_LOCATIONS parameter restrict or block access to these buckets, respectively, when stages that reference this integration are created or modified\n * **growthlop\\_role** is the role associated to the service account used by GrowthLoop for querying snowflake\n * Create **External Stage** in Snowflake\n \n * Run the following SQL Command in Snowflake\n \n ```\n USE ROLE ACCOUNTADMIN;\n CREATE OR REPLACE STAGE flywheel_external_stage\n URL='s3://exports//'\n STORAGE_INTEGRATION = flywheel_app_aws\n \n GRANT OWNERSHIP ON integration FLYWHEEL_APP_AWS to ROLE \n ```\n \n * **NOTE:** The Storage Integration must be created in the FLYWHEEL\\_SYSTEM Schema\n * Where:\n * **iam\\_role** is the Amazon Resource Name (ARN) of the IAM role you created above.\n * **bucket** is the name of a S3 bucket that stores your data files (e.g. mybucket). The required STORAGE\\_ALLOWED\\_LOCATIONS parameter and optional STORAGE\\_BLOCKED\\_LOCATIONS parameter restrict or block access to these buckets, respectively, when stages that reference this integration are created or modified\n * **growthlop\\_role** is the role associated to the service account used by GrowthLoop for querying snowflake\n * **org\\_id** Please ask your GrowthLoop Solutions Architect to provide you with your specific org\\_id\n * **Retrieve the AWS IAM User for your Snowflake Account**\n \n * To retrieve the ARN for the IAM user that was created automatically for your Snowflake account, use the DESCRIBE INTEGRATION.\n \n ```\n DESC INTEGRATION GROWTHLOOP_APP_AWS;\n ```\n \n * Record the values for the following properties in the response:\n * STORAGE\\_AWS\\_IAM\\_USER\\_ARN: The AWS IAM user created for your Snowflake account; for example, arn:aws:iam::123456789001:user/abc1-b-self1234. Snowflake provisions a single IAM user for your entire Snowflake account. All S3 storage integrations in your account use that IAM user.\n * STORAGE\\_AWS\\_EXTERNAL\\_ID: The external ID that Snowflake uses to establish a trust relationship with AWS. If you didn’t specify an external ID (STORAGE\\_AWS\\_EXTERNAL\\_ID) when you created the storage integration, Snowflake generates an ID for you to use.\n * You provide these values in the next section.\n * **Grant the IAM User Permissions to Access Bucket Objects**\n \n * Log in to the AWS Management Console.\n * Select IAM.\n * From the left-hand navigation pane, select Roles.\n * Select Role created above.\n * Select Trust relationships tab.\n * Select Edit Trust Policy\n * Modify the policy document with the DESC STORAGE INTEGRATION output values you recorded.\n \n ```\n {\n \"Version\": \"2012-10-17\",\n \"Statement\": [\n {\n \"Sid\": \"\",\n \"Effect\": \"Allow\",\n \"Principal\": {\n \"AWS\": \"\"\n },\n \"Action\": \"sts:AssumeRole\",\n \"Condition\": {\n \"StringEquals\": {\n \"sts:ExternalId\": \"\"\n }\n }\n }\n ]\n }\n ```\n \n * Where:\n * **snowflake\\_user\\_arn** is the STORAGE\\_AWS\\_IAM\\_USER\\_ARN value you recorded.\n * **snowflake\\_external\\_id** is the STORAGE\\_AWS\\_EXTERNAL\\_ID value you recorded.\n * Select Update Policy to save changes.\n * **Create an IAM user for GrowthLoop**\n \n * Log in to the AWS Management Console.\n * Select IAM.\n * From the left-hand navigation pane, select Users.\n * Select Create User.\n * Create user for GrowthLoop and assign IAM Role created above.\n * Generate an access key and secret access key for the new user.\n * Click save\n * You will use this access key and secret access key in [Setup External Storage in GrowthLoop](https://docs.growthloop.com/docs/bring-your-own-bucket#setup-external-storage-in-growthloop)\n\nTo set GCS as your storage bucket follow these steps:\n\n* Create a new GCS bucket in your account.\n * Make sure to block public access\n * Setup a TTL time of your choice to enhance security\n* Create a GCP service account for a user with the following permissions:\n\n| Permission | Details |\n| --- | --- |\n| storage.objects.list | List objects in a bucket |\n| storage.objects.create | Create objects in a bucket |\n| storage.objects.get | Get objects in a bucket |\n| storage.buckets.get | Get metadata on a bucket |\n\n* [Create Credentials](https://developers.google.com/workspace/guides/create-credentials#create_credentials_for_a_service_account) for your Service Account.\n * In the Google Cloud console, go to Menu menu > IAM & Admin > Service Accounts.\n * Select your service account.\n * Click Keys > Add key > Create new key.\n * Select JSON, then click Create. Your new public/private key pair is generated and downloaded to your machine as a new file. Save the downloaded JSON file as credentials.json in your working directory.\n * You will use the `credentials.json` file in [Setup External Storage in GrowthLoop](https://docs.growthloop.com/docs/bring-your-own-bucket#setup-external-storage-in-growthloop)\n * Click Close.\n\nOnce you have your bucket ready along with the correct credentials, head over to **Organization** under Settings in the GrowthLoop application. Navigate to the **Storage** tab.\n\n![](https://files.readme.io/68ca677a4513d1f0183a4f60b01e2b12f00e639dd01503ec50e8d3b9df54d604-Screenshot_2024-08-28_at_10.11.44_PM.png)\n\n![Setting up GCS Storage Bucket](https://files.readme.io/ceac268f724dc219d5842a9c289bfc8d6f68ba6413ac919a22ab16ee0afe7bce-Screenshot_2024-08-28_at_10.00.30_PM.png)\n\nSetting up GCS Storage Bucket\n\nSelect your bucket platform and provide the necessary credentials then hit save. That's it! Our platform will now use your secure bucket for any staging of data.\n\nIf you experience any issues or have any questions, please reach out to us at [Solutions@GrowthLoop.com](mailto:solutions@growthloop.com), and we’ll be in touch shortly!\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:32.676Z","23310ad1-909b-4735-bc7b-043ba7d41032",[],[],{"_40":1041,"_128":1042,"_130":1043,"_132":1044,"_134":-5,"_13":-5,"_120":1045,"_122":136,"_25":1046,"_138":-5,"_139":1047,"_141":1048},"How to troubleshoot issues with Google Ads | GrowthLoop Docs","how-to-troubleshoot-issues-with-google-ads-growthloop-docs","https://docs.growthloop.com/docs/google-ads-troubleshooting-adding-growthloop-to-allowlist","# How to troubleshoot issues with Google Ads\n\n## Google Ads Troubleshooting\n\nWhen setting up Google Ads as a destination in the GrowthLoop app, one of the first steps is to login with your Google Ads account credentials. It is important, though, to ensure your Workspace Admin has first enabled GrowthLoop on your AllowList of apps. If they have not, you will see \"This app is blocked\" when attempting to connect your account.\n\n![](https://files.readme.io/13c5f5b-Untitled.png)\n\n‍ \nHere is how to resolve this issue. Have your Google Workspace admin follow the steps below:\n\n1. Go to: [https://admin.google.com/](https://admin.google.com/)\n2. Go to: **Security**\n\n![](https://files.readme.io/ac5eaa2-Untitled_1.png)\n\n3. Scroll down and click on **API controls**\n\n![](https://files.readme.io/e53c340-Untitled_2.png)\n\n4. Select **Configure New App**\n\n![](https://files.readme.io/2a6c673-Untitled_3.png)\n\n5. Search for **GrowthLoop's Client ID**: 983574759527-ukr43reakji8pm7qqent6d9navdikg34.apps.googleusercontent.com\n6. Select **Audience Router**\n\n![](https://files.readme.io/6aa1491-Untitled_4.png)\n\n7. Select the Client ID for Audience Router and go to next step\n\n![](https://files.readme.io/e27a736-Untitled_5.png)\n\n8. Select **\"Trusted: Can access all Google services\"**\n9. Select **Configure**\n\n![](https://files.readme.io/81223bc-Untitled_6.png)\n\n10. You are all set! GrowthLoop is now in your App Access Control Panel as a Connected App.\n11. Now go ahead and try to add your Google Ads Destination in the GrowthLoop app. \n ‍ \n **Note**: You also need to ensure your Google Ads representative has turned on \"Customer Match\". Contact your Google Ads rep to ensure this in place. Or try to connect your account in GrowthLoop and we'll let you know if it isn't turned on yet.\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:30.908Z","c499b233-225c-44c1-b344-bcde461c6032",[],[],{"_40":1050,"_128":1051,"_130":1052,"_132":1053,"_134":-5,"_13":-5,"_120":1054,"_122":136,"_25":1055,"_138":-5,"_139":1056,"_141":1057},"How to use data to create an audience | GrowthLoop Docs","how-to-use-data-to-create-an-audience-growthloop-docs","https://docs.growthloop.com/docs/create-an-audience","# How to use data to create an audience\n\nIn this tutorial, you will learn how to create an audience in the GrowthLoop app using data directly from your data warehouse. Need a refresher on what an audience is?\n\nCheck out [Intro to Audiences](https://docs.growthloop.com/docs/intro-to-audiences).\n\nFirst, **navigate to Audience** under Platform in the GrowthLoop app on the left hand side. This will bring you to the **Central Audience Hub** where you can view, filter, and search all your organization’s audiences.\n\nTo create an audience, click **New Audience** in the upper right hand corner of the Central Audience Hub.\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd845cb181cb47_ta0PY4ZNnSpGXoje0I4R1H0fmb9Y-BpjrfIBPR66d7vOFNRSeKLc4qf8_c30Gd0jVnIP-nkrq4Wezqo10qFE0pIrKaupuc7AMaHTHsH61MN9giCAD4FYNhQ63M7bVylJqDxhhFUMNIQPwxDw-jyJmcY.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd845cb181cb47_ta0PY4ZNnSpGXoje0I4R1H0fmb9Y-BpjrfIBPR66d7vOFNRSeKLc4qf8_c30Gd0jVnIP-nkrq4Wezqo10qFE0pIrKaupuc7AMaHTHsH61MN9giCAD4FYNhQ63M7bVylJqDxhhFUMNIQPwxDw-jyJmcY.png)\n\nIf you read [Intro to Audiences](https://docs.growthloop.com/docs/intro-to-audiences), you’ll know you have 3 options to start building your first audience. Take your pick, but starting with the basics is recommended and then you can adjust from there.\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd84de3281cb48_uvaO3CyuP1M57lbXc_7qKDTkTLm3TrfInB4GZ3IFUe-RzVbvBvNaKr0nWRjysCfoJLewqkx5ojI8Jg2eWMspX-sYXR9yhD8VbR0ipEk446YuRMIjpoxi5AsajopKX_8-nxN7Gb5iGPl31adWxn7vzgQ.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd84de3281cb48_uvaO3CyuP1M57lbXc_7qKDTkTLm3TrfInB4GZ3IFUe-RzVbvBvNaKr0nWRjysCfoJLewqkx5ojI8Jg2eWMspX-sYXR9yhD8VbR0ipEk446YuRMIjpoxi5AsajopKX_8-nxN7Gb5iGPl31adWxn7vzgQ.png)\n\nOnce you click on how you want to begin building your audience, you’re off to the audience builder!\n\n_Note: Your audience builder may look slightly different as your default settings configured by your admins may vary and the datasets connected are unique to each organization.New features may have also been released after this tutorial was created._\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd84c8ad81cb49_oKjveGVZ63plf_n93zrUFNIFt4qlTxAYvN3p4ro3gwcPbLFReblpLlc503yccgBbCUsbVabc-Ig9BCfJQI7e0XwDP0B97Bjyh8OHtIPSYFOVCRP668zfM3C0qx285iVUIITBi6xuQ-rS12F0-V6K9xA.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd84c8ad81cb49_oKjveGVZ63plf_n93zrUFNIFt4qlTxAYvN3p4ro3gwcPbLFReblpLlc503yccgBbCUsbVabc-Ig9BCfJQI7e0XwDP0B97Bjyh8OHtIPSYFOVCRP668zfM3C0qx285iVUIITBi6xuQ-rS12F0-V6K9xA.png)\n\nAudience Builder landing page\n\n1. **Audience Name** Give your audience a title and it’ll automatically begin saving your audience. Under the audience name, you will find some settings that will allow you to Auto-save audiences as you change filters, as well as refresh your live audience size. You can also add tags to help organize your audiences.\n2. **Audience Inclusions and Exclusions** You can include or exclude any audiences that have been created previously in GrowthLoop from the audience you are currently creating. This is helpful if you have building block audiences that might have been previously targeted. This is not a required field to create your audience.\n3. **Customers** This is where the fun happens. Default filters are typically shown here, but these can be updated by your admin. Start creating your audience by adding filters (+, or start typing to add a filter field) based on the fields in your data warehouse customers table, and start selecting or inputting values appropriately. You can hover over a filter to see a description of that field generated from the warehouse or Marve.\n4. **Transactions & Other Data‍** You can add other transactions and events datasets to filter on objects in those datasets.‍**Transactions** dataset types typically include data that connect purchases and order details for targeting audiences by transactions.‍**Events** datasets typically include data to target users by attendance, RSVP status, and more. Note: Additional datasets need to be connected by an admin.\n5. **Audience Size** As you build out an audience, the size of the audience is automatically calculated when a filter is changed, added, or removed and populated in the top right of the screen.\n6. **Audience Insights**As you build your audiences, you can see insights into the audience you are building based on configurations selected such as Total Revenue, Treatment & Control, and audience Breakdowns.\n7. **Overview - Total Revenue** Defaulted typically to the total lifetime revenue of customers in the connected customer dataset.\n8. **Treatment & Control** You can create a treatment & control group for campaign evaluation.Simply adjust the slider left and right and you’ll notice the percentage of customers are allocated to either the treatment or control (i.e. will receive the advertisement vs not). You can read more on how we view **[campaign evaluation](https://docs.growthloop.com/docs/experiments)** here.\n9. **Breakdowns** You can see the breakdown of audiences by individual fields, increasing insight into audiences as you build them. This can help you make more educated decisions about whether or not to target a specific group. Click on the + on the right under Breakdown Report and add a field to see the report.\n10. **Comparisons** Here you will find Audience comparisons that allow you to find a pre-existing audience to compare overlap with the customers matching your current audience criteria. You can then exclude members from an audience that overlaps with another audience, to prevent double-targeting.\n11. **Export Audience** Once your audience has a title and is saved, an Export Audience button will appear at the top right under your audience size, allowing you to export your audience to your connected destinations.\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd840a9281cb4f_vh0ieBWMeZXLQqG40gXuwclOo8pl0X4_Ir6ifAiVNB-ileWEvhC5g2DmTw_7o-mLSyCXgDie--fvyRFnOF_Ei1-CbqhyQlBouDB6CLAWMrU6sPnLw_FFdNFHxySIdhT73aFpkTiaB7fANHSRdgDJGww.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd840a9281cb4f_vh0ieBWMeZXLQqG40gXuwclOo8pl0X4_Ir6ifAiVNB-ileWEvhC5g2DmTw_7o-mLSyCXgDie--fvyRFnOF_Ei1-CbqhyQlBouDB6CLAWMrU6sPnLw_FFdNFHxySIdhT73aFpkTiaB7fANHSRdgDJGww.png)\n\n* **Export:** Export the audience to one or many CRM or Ad **[destinations](https://www.growthloop.com/destinations)**, cross-channel!\n* **Edit:** Edit the audience to make adjustments. _Note: Once an audience is exported, you cannot make edits. This is to prevent any possible errors in existing activity. We recommend copying the audience, adjusting, and re-exporting._\n* **Copy:** Copy the audience to adjust filters, while keeping the original intact. Make sure to name the copied audience accordingly so that you know the difference between this audience and the original.\n* **Archive:** Archiving an audience hides this audience from the Central Audience Hub, but can be searched by archive status, with an option to copy and use again.\n* **Delete:** Delete the audience. Once this action is taken you can't revert. Consider archiving if you might want to revisit the audience.\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd84a76281cb4d_kgebXWZ8JeWZKhvQRBoNuE1sygSaCIdXhr3sbGFWEIi-H4w7oVS7O5uet7AmEuY-mEevG-PnzMk8gfuM0LXw0DJOGkyb3m9tNepsPMZp23t4ZLviaiWAUuI_ZS3j07EuF81kSVqRi4AEbISP2pNlSPs.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/6452937893cd84a76281cb4d_kgebXWZ8JeWZKhvQRBoNuE1sygSaCIdXhr3sbGFWEIi-H4w7oVS7O5uet7AmEuY-mEevG-PnzMk8gfuM0LXw0DJOGkyb3m9tNepsPMZp23t4ZLviaiWAUuI_ZS3j07EuF81kSVqRi4AEbISP2pNlSPs.png)\n\nWant to learn how to export your audience to Facebook, Adwords, or other destination platforms? Go to the Destinations **category to learn how. If you need any help, visit our**[help center](https://docs.growthloop.com/docs/welcome)**or reach out to**[support@growthloop.com](mailto:support@growthloop.com)\n\nUpdated 9 days ago\n\n* * *","2024-03-20T21:02:24.411Z","8b233018-a769-4896-a04b-5d1f5f0e0882",[],[],{"_40":1059,"_128":1060,"_130":1061,"_132":1062,"_134":-5,"_13":-5,"_120":1063,"_122":136,"_25":1064,"_138":-5,"_139":1065,"_141":1066},"How to use Insights Hub | GrowthLoop Docs","how-to-use-insights-hub-growthloop-docs","https://docs.growthloop.com/docs/insights-tab","# How to use Insights Hub\n\nLearn how to access your Insights Hub in GrowthLoop\n\nAs you start activating your data with GrowthLoop, it becomes very important to visualize performance insights on audiences and journeys in a single location. This allows your teams to see what channels and tactics are working with customers, and improve what they try next time. We built **Insights Hub** to give you a single location to get insights on audiences across any marketing and sales channel.\n\nTo access your **Insights Hub**, you can navigate to GrowthLoop and on the left hand menu look for it.\n\n![](https://files.readme.io/6c03471-image.png)\n\nBy default, you will see a few **Insight Modules** automatically unlocked on your account. In order to unlock additional modules, please contact our Support Team ([support@growthloop.com](mailto:support@growthloop.com)).\n\nHere are the available add-ons and what you can expect from them:\n\n1. **Audience overlap** (default) -- Compare membership across audiences and combine high-overlapping audiences.\n2. **Billing** (default) -- Gain visibility on your data warehouse costs on storage & compute for running the GrowthLoop platform.\n3. **Paid media measurement** -- Visualize your GrowthLoop audience performance across any supported paid media channel in a single location.\n4. **Identity resolution** -- If you're leveraging our [identity resolution (IR) module](https://docs.growthloop.com/docs/identity), use this add-on to gain visibility into your match configurations, performance comparisons between match configurations and any data quality issues with the IR process\n5. **Attribution** -- Gain a better understanding on which touchpoints and events are responsible for user conversions.\n6. **Campaign insights** -- Get a detailed analysis of uplift and conversion metrics for any audience.\n7. **Customer 360** -- A one-stop-shop to see all interactions an information for a given customer.\n\n![](https://files.readme.io/713a215-image.png)\n\nIf you have any questions or would like to enable any of these add-ons for your org, please contact [support@growthloop.com](mailto:support@growthloop.com).\n\nUpdated 18 days ago\n\n* * *","2025-06-20T22:58:06.261Z","50ee34c7-9843-4a65-a8d6-8d339078ed3f",[],[],{"_40":1068,"_128":1069,"_130":1070,"_132":1071,"_134":-5,"_13":-5,"_120":1072,"_122":136,"_25":1073,"_138":-5,"_139":1074,"_141":1075},"How to use Marve Audience Discovery | GrowthLoop Docs","how-to-use-marve-audience-discovery-growthloop-docs","https://docs.growthloop.com/docs/marve-audience-discovery","# How to use Marve Audience Discovery\n\nIn this article, you'll learn how to use Marve Audience Discovery\n\nWith Marve Audience Discovery, your teams leveraging GrowthLoop will automatically receive audience suggestions. Think about it like your \"Discovery Playlist\" on Spotify. Every week, Marve learns from the audiences created by your team members, and it will automatically suggest audiences for you to target to achieve your goals.\n\n* First, ensure you have [Marve enabled](https://docs.growthloop.com/docs/enable-marve) for your organization.\n* Click Home in the left-hand menu\n* Scroll down to \"Audience Discovery\"\n* Marve will suggest up to four audiences to target, and they will appear on your home page and in your inbox every Monday.\n* Click \"Create\" on any audience suggestion and it will take you to the audience canvas, so you can save and export the suggested audience.\n\n![](https://files.readme.io/1d84bfd-audience_discovery_docs.png)\n\n> 👍\n> \n> Marve is continously improving.\n> \n> To further understand the data used in Marve, see our [data utilization documentation](https://docs.growthloop.com/docs/enable-marve#what-data-is-used-in-marve).\n> \n> If you would like to have Marve incorporate audience conversion rate information into its recommendations to provide audience suggestions based on performance, contact [support@growthloop.com](mailto:support@growthloop.com).\n\n> 👍\n> \n> GrowthLoop uses a composable architecture at every level. If you'd like to use a custom hosted LLM to support Marve Discovery, please contact [support@growthloop.com](mailto:support@growthloop.com).\n\n> 📘\n> \n> Marve is available to customers on our enterprise plan. To enable Marve in your account, please contact your solutions architect at [support@growthloop.com](mailto:support@growthloop.com).\n\nWe hope you found this helpful. If you have any questions, please don’t hesitate to reach us at [support@growthloop.com](mailto:support@growthloop.com).\n\nUpdated 5 months ago\n\n* * *\n\nCheck out how your team can actively brainstorm audiences using natural language with Marve Studio.\n\n* [Marve](https://docs.growthloop.com/docs/marve)","2025-06-20T22:58:07.189Z","a67a8394-2b29-4278-8f40-56fe151cf97b",[],[],{"_40":1077,"_128":1078,"_130":1079,"_132":1080,"_134":-5,"_13":-5,"_120":1081,"_122":136,"_25":1082,"_138":-5,"_139":1083,"_141":1084},"HubSpot Syncs","hubspot-syncs","https://docs.growthloop.com/docs/hubspot-syncs","Enhance your HubSpot CRM with powerful customer data from your data warehouse.\n\nIn this guide, we’ll walk you through syncing customer data from your data warehouse into HubSpot to supercharge your CRM efforts. Let's get started!\n\nGrowthLoop enables syncing to these HubSpot objects:\n\n| **Object** | **Description** | **Sync Modes** | **Required Fields** | **Optional Fields** |\n| --- | --- | --- | --- | --- |\n| **Contacts** | Individuals interacting with your business, storing personal details and communication history. | Insert, Upsert, Update | `Email`: unique user identifier | `First Name`, `Last Name`, `Phone Number`, `Company`, `Job Title`, `Address`, `Lifecycle Stage` |\n| **Companies** | Organizations associated with your business, capturing company-specific information. | Insert, Upsert, Update | `Company Name`: unique company identifier | `Domain`, `Industry`, `Phone Number`, `Number of Employees`, `Address`, `Annual Revenue` |\n| **Deals** | Sales opportunities tracking potential revenue through your pipeline. | Insert, Upsert, Update | `Deal Name`: deal identifier | `Deal Stage`, `Amount`, `Close Date`, `Deal Type`, `Associated Contacts`, `Associated Companies` |\n| **Tickets** | Customer service requests or issues, facilitating support tracking and resolution. | Insert, Upsert, Update | `Ticket Name`: ticket identifier, `Pipeline`: ticket pipeline | `Ticket Status`, `Priority`, `Source`, `Description`, `Associated Contacts`, `Associated Companies` |\n| **Line Items** | Individual products or services associated with deals, detailing specifics of the transaction. | Insert, Upsert, Update | `Name`: item identifier, `Price`: unit price, `Product ID`: product identifier | `Description`, `SKU`, `Discount`, `Tax`, `Associated Deals` |\n\n* To set up Syncs in HubSpot, ensure you have an active HubSpot account and have configured it as a destination. Click [here](https://docs.growthloop.com/docs/hubspot-destination) to learn how.\n\n> 📘\n> \n> HubSpot enforces daily and per-second API rate limits. If your sync exceeds the daily limit (typically 1 million records for Enterprise plans), it may take multiple days to complete. During this time, the sync status will remain “Processing” as we pause and resume the sync across days.\n\n5. Navigate to the **Syncs** tab on the left sidebar and click **Create Sync** in the top right corner.\n6. Set up your Sync with the following details:\n 1. **Sync Name:** A clear, friendly name for your sync.\n 2. **Sync Frequency:** How often data should sync to the destination.\n 3. **Update Rule:** The default method for syncing data to the destination. GrowthLoop supports `Insert Only` (adds new records), `Update Only` (modifies existing record attributes), and `Upsert` (combines insert and update)\n 4. **Dataset / Table:** The table that contains your data.\n 5. **Dataset Unique Field:** The column with unique values for each row in the table. This will be detected and selected automatically.\n 6. **Match Field:** The column used to match data in your source table with the destination system.\n 7. **Connection:** Choose the destination for syncing data. Select **HubSpot**.\n 8. **Object Type:** Select the object to sync data. Your options are: `Contacts`, `Companies`, `Deals`, `Tickets`, `Line Items`\n 9. **Match Field:** The column used to match data in the destination system with your source table.\n7. After selecting/inserting the required information, click **Save Sync**.\n8. Next, set up the field mappings to start your sync. Please refer to the **Support Objects** table at the top of the page. For this example, we will set up a sync to `Contacts`, which requires **Email**. We'll also map the optional field **First Name** along with it.\n9. Under **Source**, open the drop-down and select the field containing email addresses.\n10. In the **Destination** section, choose **Email** from the drop-down menu, unless already selected.\n11. Click **Add Mapping** to add another **Source > Destination** row.\n12. In the **Source** section, select the field containing the first name for each contact.\n13. Then under **Destination**, choose **First Name** from the drop-down menu, unless already selected.\n14. After mapping all the fields, clicking **Update Sync** will prompt you with the following two options:\n 1. **Updates Only:** We recommend you go with the this option, especially if you’re setting up the sync for the first time.\n 2. **Back-fill**: This option is when you are updating an existing Sync with newly mapped fields and you’d like all your **already synced events** to have those fields backfilled for them. This operation can be very expensive and time consuming on your underlying Data Warehouse, so please choose that option if you’re absolutely sure.\n15. Once complete, return to your sync and enable it by clicking the **toggle** at the top of the page.\n16. To confirm that your sync has been successfully sent to HubSpot, login to your account and navigate to the **CRM** section. Here is where you can view the newly inserted records and attributes.\n\n![The emails that appear in this image are fake](https://files.readme.io/8eca54babab0079d49b631bcae692fca8aec256526400f4d6360a3e1072059cc-image.png)\n\nThe emails shown in this image are not real\n\n> 👍\n> \n> You have successfully created a sync to `Contacts` in HubSpot!\n\n> 📘\n> \n> If you experience any issues when connecting to or creating syncs to HubSpot, please reach out to us at [support@growthloop.com](mailto:support@growthloop.com), and we’ll be in touch shortly to help resolve the matter!\n\nUpdated 5 months ago\n\n* * *","2025-06-20T22:58:04.235Z","fb90d7fd-750b-4290-8956-4be7fa20c275",[],[],{"_40":1086,"_128":1087,"_130":1088,"_132":1089,"_134":-5,"_13":-5,"_120":1090,"_122":136,"_25":1091,"_138":-5,"_139":1092,"_141":1093},"Identity Resolution in your data cloud | GrowthLoop Docs","identity-resolution-in-your-data-cloud-growthloop-docs","https://docs.growthloop.com/docs/identity","# Identity Resolution in your data cloud\n\nLearn how our identity resolution module can accelerate your identity programs.\n\nIn this article, we'll walk through GrowthLoop's approach to identity resolution module and a step-by-step playbook of how we help customers implement identity resolution directly in their data cloud.\n\nGrowthLoop's identity module was designed with a few key principles in mind:\n\n1. **Runs in your Data Cloud:** Data should not have to leave your data cloud to run your identity process.\n2. **Deterministic Matching:** For identity projects it is important to start with exact deterministic matching on user attributes people understand (ie. email, phone, date of birth, name, address). This builds confidence with marketing and helps your project gain momentum.\n3. **Rapid Testing:** GrowthLoop identity module is optimized to help organizations quickly configure match rules, run the identity process, evaluate results and repeat. This \"Identity Cycle\" is designed to be fast and repeatable to get you to the right identity profile faster.\n4. **Persistent Keys:** GrowthLoop provides a persistent identifier on every golden record.\n5. **Transparency:** Your identity solution should be fully transparent. GrowthLoop produces tables at each step in the process that your team can see in your data cloud to understand what happens at every step.\n6. **Always On:** GrowthLoop Identity is an always-on process that will match new records so they become available to your team quickly. And provides your team the ability to monitor your identity processing for any anomalies before they cause issues downstream.\n\n \n\n1. Click on **Organization** in the left-hand menu. Note: You must have a user role that has permission to access organization management. If you do not see \"Organization\" in the menu, contact your GrowthLoop administrator.\n2. Click on **Source Connections** tab\n3. Create a **[Source Connection](https://docs.growthloop.com/docs/source-connection-management#create-new-source-connection)**\n 1. Ensure your authentication credentials you use to setup your Source Connection have access to the source tables in your data cloud that will be used in the Identity Module.\n\n \n\n1. Design your first Match Rule:\n 1. Identify a set of Match Keys (ie. First Name, Last Name, Date of Birth)\n 2. Map each source table's columns to the match keys (ie. first\\_name -> First Name)\n 3. Assign a priority to your Match Rule. If you only have one Match Rule, it will be automatically evaluated first.\n 4. **Note:** GrowthLoop will standardize match keys such as dates, phone numbers, and addresses to achieve a higher match rate.\n2. Design additional Match Rules and assign priority.\n 1. You can create up to 5 Match Rules\n 2. For each additional match rule, you will assign a priority to the Match Rule.\n3. Note: How Match Rules are evaluated:\n 1. Every record processed will be matched to records in other source tables leveraging the highest priority Match Rule.\n 2. The record will then be matched leveraging the additional Match Rules according to their priority order.\n\n![](https://files.readme.io/1c3fec8-Match_Rule_Cascading.png)\n\n1. Run the Identity Module\n2. Processing will occur in your data cloud following the processing steps in the diagram below.\n\n![](https://files.readme.io/b462a88-Screen_Shot_2024-03-04_at_3.49.21_PM_1.png)\n\n3. Identity Module will provide the following outputs in your data cloud:\n\n**Lookup Table:** The Lookup table is a union of all the source tables. During this first step, we align the necessary columns of these disparate tables into a uniform schema. The columns of this table will be the set of columns the user has chosen to appear in the Golden Table, along with some metadata. This table is also responsible for adding columns for nickname and the standardized address. If the end user has selected to use a 3rd party identity graph, this table will also populate the 3rd party identity id.\n\nTable name: _id\\_res\\_lookup_\\[identity\\_id\\]\n\nExample Table Schema:\n\n![](https://files.readme.io/e7d2645-Screen_Shot_2024-05-14_at_9.42.47_AM.png)\n\n* * *\n\n**Match Table:** This table contains all of the data from the Lookup Table, but with an additional column for the match\\_id. This step is where all of the matching logic occurs.\n\nTable name: _id\\_res\\_matched_\\[identity\\_id\\]\n\nTable Schema: (plus whatever columns appear in the Lookup Table)\n\n![](https://files.readme.io/9ce3437-Screen_Shot_2024-05-14_at_9.52.15_AM.png)\n\n* * *\n\n**Golden Table:** The Golden Table is ultimately the desired output from this whole process. This table will only contain the columns which the user has chosen to appear in the Golden Table. The data in this table represents a golden customer record, and is essentially the data from the Matched Table, but deduplicated on match\\_id.\n\nTable name: _id\\_res\\_golden_\\[identity\\_id\\]\n\nExample Table Schema:\n\n![](https://files.readme.io/489e8bb-Screen_Shot_2024-05-14_at_9.55.49_AM.png)\n\n* * *\n\n**Golden Profile Report Table:** This is the output final table of the process. This table contains metrics which represent a set of statistics and data quality checks which populates a dashboard to give the user a visual understanding of how their match rules and customer data are performing over time.\n\nTable name: _id\\_res\\_golden\\_profile\\_report_\\[identity\\_id\\]\n\nExample Table Schema:\n\n![](https://files.readme.io/34fff6c-Screen_Shot_2024-05-14_at_10.04.17_AM.png) ![](https://files.readme.io/8b2c08d-Screen_Shot_2024-06-24_at_2.44.16_PM.png) ![](https://files.readme.io/8918205-Screen_Shot_2024-06-21_at_12.21.57_PM.png)\n\n* * *\n\n \n\n1. Every Identity Module Run produces a Golden Profile Report\n2. This report provides you with key metrics on your identity run, and metric averages for comparison to previous identity runs.\n 1. **golden\\_column\\_had\\_conflicting\\_data\\_count**: Tracks the number of columns in the golden table which had conflicting values when deduplicating. A high number for this metric may indicate the columns included in match rules should be expanded.\n 2. **golden\\_records\\_had\\_conflicting\\_data\\_count**: Total count of matched source records which conflicted on a non-match field chosen to appear in the golden table. A high number for this metric similarly may indicate the columns included in match rules should be expanded.\n 3. **max\\_sources\\_for\\_golden\\_record**: Captures the maximum number of source records matched to a single golden record. Any golden customer rows which are anomalous in by this metric should be reviewed by a human to check for data quality issues.\n 4. **match\\_rules**: Specifies the match rules applied across different steps in the data matching process.\n 5. **source\\_records\\_not\\_matched\\_count**: Count of source records that didn't find a match in the golden table.\n 6. **source\\_records\\_total\\_count**: Total count of individual source records.\n 7. **matched\\_table\\_record\\_count**: Total count of records that matched between source and golden tables.\n 8. **source\\_records\\_matched\\_count**: Count of source records that found a match in the golden table.\n 9. **golden\\_table\\_record\\_count**: Total count of records in the golden table.\n 10. **lookup\\_table\\_record\\_count**: Total count of records in the lookup table.\n 11. **matched\\_rows\\_rule\\_1\\_count**: Number of rows matched based on the first match rule. There will be an additional column for each additional match rule provided. These metrics provide insight into which match rules are most influential. This helps determine if certain match rules should be removed, modified or swapped in priority for the ideal match configuration.\n 12. **golden\\_table\\_duplicate\\_email\\_count**: Count of duplicate email addresses found in the golden table. This is a data quality metric which indicates potential issues with the match configuration, depending on the expected result. It typically means the match configuration should be adjusted, or, an additional deduplication step should be added.\n3. Review the Golden Profile report, and repeat Step 2 to refine your Match Rules, and rerun your Identity Module.\n\n1. Add key fields to your Golden Record Table to be used in audience building in GrowthLoop (ie. Total spend last 12 months).\n2. For each Golden Profile you can leverage the Lookup Table to aggregate key metrics like spend from source tables, and place them as additional fields on the Golden Record Table.\n3. You can leverage [GrowthLoop Models](https://docs.growthloop.com/docs/models) to add new attributes to your Golden Profile directly within the GrowthLoop application..\n\nGrowthLoop's solutions team has effectively managed Fortune 500 identity projects. We have a well-honed playbook and will be with your team every step of the way. One of the most important things to note about identity projects is how the process is managed. If managed well, you can iterate quickly and build confidence in your organization within 6 weeks. If identity projects are managed poorly, the project will drain resources, and not be trusted by marketing. We help make sure your Identity work follows the first path.\n\nOnce you have your Golden Profile in your data cloud you are ready to activate. Set up your new Golden Profile in a [new Dataset Group](https://dash.readme.com/project/growthloop/v1.0/docs/setup-dataset-group) and begin creating audiences.\n\nIf you have any questions about our Identity Module and Playbook, please contact [support@growthloop.com](mailto:support@growthloop.com).\n\nUpdated 3 months ago\n\n* * *","2025-06-20T22:58:27.538Z","f6edb7af-0084-43c8-963e-2d65d217822f",[],[],{"_40":1095,"_128":1096,"_130":1097,"_132":1098,"_134":-5,"_13":-5,"_120":1099,"_122":136,"_25":1100,"_138":-5,"_139":1101,"_141":1102},"Integrate GrowthLoop into your platforms | GrowthLoop Docs","integrate-growthloop-into-your-platforms-growthloop-docs","https://docs.growthloop.com/docs/overview-embed","# Integrate GrowthLoop into your platforms\n\n## Overview\n\nLearn how to integrate GrowthLoop into your platforms\n\nPowered by GrowthLoop provides a few options for integrating composable audiences and journeys into your existing platforms:\n\n* [**Personalization API**](https://docs.growthloop.com/docs/personalization-api-1): Looking to personalize your mobile application or website based on real-time customer profile and segment information, then the Personalization API is what you are looking for. It enables you to pass a user identifier to our real-time API and receive an instant customer profile and segments the user is in so you can use the information to personalize their experience.\n* [**GrowthLoop API:**](https://docs.growthloop.com/reference/get_api-public-exports) Use GrowthLoop's API to trigger exports from internal workflows or fully embed audience lists in your applications.\n* [**Powered by GrowthLoop Embed**](https://docs.growthloop.com/docs/embed) Looking to embed Audience and Journey building in your custom-built application? You can now embed GrowthLoop directly into your application to give your users an audience builder that can export to any marketing destination with our `Powered by GrowthLoop Embed`.\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:32.875Z","8bf44e70-069c-4c19-bacb-fbd378966c6d",[],[],{"_40":1104,"_128":1105,"_130":1106,"_132":1107,"_134":-5,"_13":-5,"_120":1108,"_122":136,"_25":1109,"_138":-5,"_139":1110,"_141":1111},"Integrate GrowthLoop with Salesforce Marketing Cloud","integrate-growthloop-with-salesforce-marketing-cloud","https://docs.growthloop.com/docs/intergrate-with-salesforce-marketing-cloud","GrowthLoop supercharges Salesforce Marketing Cloud by unlocking the power of your entire modern data stack. This guide will walk you through how GrowthLoop integrates with Marketing Cloud and how to use them together to drive value for your team.\n\n![](https://files.readme.io/aa0b10f-image.png)\n\nMarketing Cloud automates, personalizes, and optimizes marketing campaigns across multiple channels. However, the effectiveness of these campaigns often depends on the quality and scope of the data you provide, which is usually limited to data placed in Salesforce. Other valuable signals, such as transactions and events, are often siloed in disparate systems or buried in your Data Cloud, incurring additional costs. With Salesforce sunsetting their Audience Builder, GrowthLoop steps in as a great alternative for Marketing Cloud, integrating seamlessly to enable you to:\n\n1. Create highly defined audiences based on various data points in your Data Cloud.\n2. Export these segments directly to Marketing Cloud for targeted email campaigns.\n3. Orchestrate seamless omnichannel campaigns across email, SMS, push notifications, and social media.\n4. Measure performance across different customer segments used in Marketing Cloud from a central location.\n\nUnlocking the power of your Data Cloud with a composable CDP like GrowthLoop offers numerous ways to enhance customer experiences and marketing results. Here are some popular examples:\n\nGrowthLoop's Audience Builder was built as the easiest self-service way for marketers to create audiences for Salesforce Marketing Cloud campaigns. GrowthLoop enables marketing teams to build audiences directly on your data cloud data where they can utilize all of their organization’s data when defining audiences, not just CRM data. This includes data science predictions, internal data like coupon assignments, experiment labels, and more. Here's how to do it:\n\n1. **Define Audiences:** Use GrowthLoop to create highly defined audiences based on various data points in your Data Cloud.\n2. **Export Audiences to Salesforce:** Export these segments directly to Marketing Cloud as a Data Extension.\n3. **Send Campaigns:** Use Marketing Cloud to send targeted email campaigns to these segments.\n\n![](https://files.readme.io/03c94e0-image.png)\n\n**Step-by-Step Breakdown**\n\n1. **Creating an Audience in GrowthLoop:**\n \n 1. Navigate to Audiences:\n 1. In the GrowthLoop app, on the left-hand side menu, click on \"Audience\".\n 2. Create a New Audience:\n 1. In the top right corner of the Central Audience Hub, click on \"New Audience\".\n 3. Define Your Audience Criteria:\n 1. Give your audience a descriptive name.\n 2. Utilize the builder to define your audience criteria. You can add filters based on various data points from your connected data sources.\n 3. _Example: Target users who have made a purchase in the last 3 months and live in California._\n 4. Refine Your Audience (Optional):\n 1. Use the \"Breakdown Report\" section to see a breakdown of your audience based on specific attributes.\n 2. Utilize \"Comparisons\" to compare your current audience with existing ones and potentially exclude overlapping segments.\n2. **Exporting an Audience to Marketing Cloud:**\n \n 1. Save and Export:\n \n 1. Once you're satisfied with your audience definition, click \"Save\" in the top right corner.\n 2. After saving, an \"Export Audience\" button will appear. Click this button.\n 2. Choose Export Destination:\n \n 1. Select \"Salesforce Marketing Cloud\" as the export destination.\n \n 2. Specify the “Business Unit MID” you want to create the Data Extension under. To locate your Business Unit in Salesforce, navigate to the top right corner of the main welcome menu. A drop-down menu will appear with all business units and their MIDs.\n \n ![](https://files.readme.io/50db7db-image.png)\n 3. Specify the specific “Data Folder Category ID” you want to create the Data Extension under. In Salesforce Marketing Cloud, it can be found by hovering over the target folder and copying the ID next to “categoryid”.\n \n ![](https://files.readme.io/86bebd5-image.png)\n \n 4. Select the additional fields you would like to include in the Data Extension under “Personalization Fields.”\n \n 3. Export Confirmation:\n \n 1. Click \"Export\" to confirm and send your audience segment to Marketing Cloud. A Sendable Data Extension will be created using the name of the audience.\n3. **Sending a Email Campaign in Marketing Cloud:**\n \n 1. Navigate to Email Studio:\n 1. Within Marketing Cloud, navigate to the \"Email Studio\" section.\n 2. Create a New Email:\n 1. Click on \"New Email\" to begin crafting your email campaign.\n 3. Design Your Email Content:\n 1. Use the drag-and-drop editor or HTML to design your email content, including images, text, and calls to action. To incorporate the additional fields you specified earlier as dynamic content for personalization in your emails, see the [instructions here](https://docs.growthloop.com/docs/intergrate-with-salesforce-marketing-cloud).\n 4. Select Your Audience:\n 1. In the \"Recipients\" section, choose \"Data Extension\" as the send source.\n 2. Select the specific GrowthLoop audience segment you previously exported.\n 5. Set Up Sending Options:\n 1. Define the sender email address, subject line, and other sending options like tracking and reporting preferences.\n 6. Schedule or Send:\n 1. Schedule your email campaign for a later date or send it immediately. To turn your one-off emails into ongoing campaigns, define a recurring export frequency in GrowthLoop. Options include \"Daily,\" \"Weekly,\" or a custom schedule based on your needs. This ensures your targeted audience segment is continuously updated in Marketing Cloud, capturing new subscribers who meet your criteria.\n\nYou can leverage GrowthLoop audiences to trigger when a user should enter a Salesforce Marketing Cloud Journey. This allows you to automate personalized journeys based on specific subscriber interactions or data points. Here's how to do it:\n\n1. **Create an Audience:** Define your target audience in GrowthLoop using various data points from your Data Warehouse.\n \n2. **Export the Audience:** Export this audience as a Data Extension to Marketing Cloud.\n \n3. **Set Up Journey:** In Marketing Cloud, use the exported Data Extension as the entry source in Journey Builder.\n \n4. **Launch Journey:** Launch the journey to engage with your audience through multiple channels, such as email campaigns, SMS, and push notifications.\n \n ![](https://files.readme.io/a7e5c02-image.png)\n \n\n**Step-by-Step Breakdown**\n\n1. **Creating an Audience in GrowthLoop:**\n \n 1. [Create](https://docs.growthloop.com/docs/intergrate-with-salesforce-marketing-cloud#growthloop--marketing-cloud-use-cases) a GrowthLoop Audience.\n2. **Exporting an Audience to Marketing Cloud:**\n \n 1. [Export](https://docs.growthloop.com/docs/intergrate-with-salesforce-marketing-cloud#growthloop--marketing-cloud-use-cases) the GrowthLoop Audience as a Data Extension to Marketing Cloud.\n3. **Create Marketing Cloud's Journey and target your GrowthLoop Audience:**\n \n 1. Open Journey Builder:\n 1. Click on \"Journey Builder\" in the main navigation menu.\n 2. Name and Configure Your Journey:\n * Enter a name and optional description.\n * Click \"Next.\"\n 3. Select Journey Type:\n * Choose \"Multi-Step Journey\" (or your desired type).\n * Click \"Next.\"\n 4. Select Entry Source:\n * Select \"Data Extension.\"\n * Click \"Next.\"\n 5. Choose Data Extension:\n * Click \"Choose Data Extension.\"\n * Select the specific GrowthLoop audience segment you previously exported.\n * Click \"Next.\"\n 6. Configure Entry Settings:\n * Set how contacts enter the journey. Marketing Cloud Journey Builder offers three entry options for contacts. Choose the option that aligns with your journey's goal and desired contact behavior:\n * **No Re-entry:** Contacts enter once, ideal for linear journeys with a clear end (welcome series).\n * **Re-entry Anytime:** Contacts can re-enter for ongoing engagement (weekly promotions).\n * **Scheduled Entry:** Contacts enter at a specific pre-defined time (birthday greetings).\n * Apply any filters as needed.\n * Click \"Done.\"\n 7. Design Your Journey:\n * Drag and drop activities (Email, SMS, Wait, etc.) onto the canvas.\n * Configure each activity by clicking on it.\n 8. Activate the Journey:\n * Congratulations! You've successfully executed a Marketing Cloud Journey to a GrowthLoop audience. If you chose to set the audience as a recurring export in GrowthLoop, contacts will be added to the data extension and will continue to enter the journey on an ongoing basis.\n\nOpt-outs from email communications don't have to derail your marketing efforts. They simply signal a preference for other channels. With Growthloop, you gain access to over 100 destinations, such as Paid, SMS, Push, Direct Mail, and more. This ensures you can seamlessly engage customers through their preferred channels. Here's how:\n\n1. **GrowthLoop:** Define an audience of recent unsubscribes using unsubscribe events and date filters.\n \n2. **Export:** Send this unsubscribe audience to a paid media provider like Google Ads.\n \n3. **Launch campaign:** Launch a display campaign on Google Ads, targeting unsubscribes to re-engage them.\n \n ![](https://files.readme.io/f77efba-image.png)\n \n\n**Step-by-Step Breakdown**\n\n1. **Creating an Audience in GrowthLoop:**\n \n 1. [Create](https://docs.growthloop.com/docs/intergrate-with-salesforce-marketing-cloud#growthloop--marketing-cloud-use-cases) a GrowthLoop Audience with unsubscribe events and date filters.\n2. **Exporting an Audience to Marketing Cloud:**\n \n 1. [Export](https://docs.growthloop.com/docs/intergrate-with-salesforce-marketing-cloud#growthloop--marketing-cloud-use-cases) the GrowthLoop Audience to Google Ads.\n3. **Launching a Display Campaign in Google Ads:**\n \n 1. Choose Your Audience:\n 1. Select the custom audience you exported in the \"Audiences\" section of Google Ads.\n 2. Start a Display Campaign:\n 1. Click \"Campaigns,\" then \"Create campaign\" and choose \"Display\" as the campaign type.\n 3. Set Campaign Goals (Optional):\n 1. Define goals like \"Website traffic\" or \"Brand awareness\" to optimize your campaign.\n 4. Configure Settings:\n 1. Under \"Networks,\" choose \"Display Network.\"\n 2. Set locations, languages, budget, and bidding strategy.\n 5. Target Your Custom Audience:\n 1. In the \"Targeting\" tab, under \"Audience targeting,\" browse and select your custom audience.\n 6. Create Compelling Ads:\n 1. Design responsive display ads with visuals, copy, and calls to action that resonate with your target audience.\n 7. Launch and Monitor:\n 1. Review your campaign settings and launch it.\n 2. Track performance using Google Ads reporting tools and optimize based on data.\n\nPersonalization is crucial for keeping your subscribers engaged. Utilize user attributes in your Data Cloud to craft emails that are highly relevant and captivating. By tailoring your content based on individual preferences and behaviors, you'll boost engagement and conversion rates. Here's how:\n\n1. **Define Your Audience in GrowthLoop:** Build an audience using relevant subscriber data (e.g., purchase history, preferences).\n \n2. **Export the Audience:** Send this targeted audience to Marketing Cloud as a Data Extension.\n \n3. **Craft Your Email in Marketing Cloud:**\n \n * Design your email using the drag-and-drop editor.\n * Include personalization strings with double percent signs (e.g., %%FirstName%%).\n4. **Schedule or Send:** Schedule your personalized email campaign or send it immediately.\n \n ![](https://files.readme.io/6dfde5a-image.png)\n \n \n \n\n**Step-by-Step Breakdown**\n\n1. **Creating an Audience in GrowthLoop:**\n \n 1. [Create](https://docs.growthloop.com/docs/intergrate-with-salesforce-marketing-cloud#growthloop--marketing-cloud-use-cases) a GrowthLoop Audience with data for personalization, such as names, purchase history, website behavior, or preferences.\n2. **Exporting an Audience to Marketing Cloud:**\n \n 1. [Export](https://docs.growthloop.com/docs/intergrate-with-salesforce-marketing-cloud#growthloop--marketing-cloud-use-cases) the GrowthLoop Audience as a Data Extension to Marketing Cloud.\n3. **Leverage Your User Record Data in Marketing Cloud Campaigns:**\n \n 1. Navigate to Email Studio:\n * Within Marketing Cloud, locate the \"Email Studio\" section.\n 2. Create a New Email:\n * Click on \"New Email\" to begin crafting your campaign.\n 3. Design Your Email Content:\n * Use the drag-and-drop editor or HTML to design your email content, including images, text, and calls to action.\n 4. Insert Personalization Strings:\n * Surround the data extension field name with double percent signs (e.g., %%FirstName%%).\n * Marketing Cloud will replace these with the corresponding data from each subscriber's record in the data extension.\n 5. Schedule or Send**:**\n * Once satisfied, schedule your personalized email campaign for a later date or send it immediately.\n\nGrowthLoop Journeys automates personalized customer journeys across channels from your Data Cloud. Using GrowthLoop's Journey Builder, marketers can orchestrate journeys across 100+ destinations alongside Marketing Cloud, access organizational data, use data science predictions, and gain visibility for analysis. Here's how to create a basic journey to export new customers for onboarding emails:\n\n1. **Create an Audience:** Define your target audience in GrowthLoop using various data points, such as new customer acquisitions.\n \n2. **Build the Journey:** In GrowthLoop, navigate to the Journeys section and create a new journey.\n \n3. **Configure and Export:** Set the journey's entry audience to newly acquired customers, add a Destination Node, and configure it to export the audience to Marketing Cloud as a Data Extension.\n \n4. **Send Onboarding Emails:** In Marketing Cloud's Email Studio, use the exported Data Extension as the audience for your onboarding email campaign. Design and send personalized welcome emails to engage your new customers.\n \n ![](https://files.readme.io/429171a-image.png)\n \n\nBefore we walk through how this setup works, there are several key benefits to having your journeys live in a Composable CDP.\n\n* **Unified Marketing Channels:** Craft journeys across **many different marketing channels**, not just what Salesforce Marketing Cloud supports today. This lets you reach your audience in all the places they hang out online.\n* **Data-Driven Decisions:** Use **all your company's data**, like surveys, purchase history, and even predictions from your data scientists, to personalize each step of your journey. This ensures your messages are relevant and timely.\n* **Enhanced Collaboration:** **Data teams can see exactly what journeys are running** and how users interact with them. This allows for better collaboration between marketing and data teams for optimal campaign performance.\n* **Global Flexibility:** **Different regions can use their preferred marketing tools**, while still leveraging the same journey builder in GrowthLoop. This provides flexibility without sacrificing consistency.\n* **Avoid Vendor Lock-in:** **You're not locked into a single marketing tool.** GrowthLoop lets you easily switch marketing tools if needed, and you always own your data.\n\n**Step-by-Step Breakdown**\n\n1. **Define Your Target Audience in GrowthLoop:**\n \n 1. [Create](https://docs.growthloop.com/docs/intergrate-with-salesforce-marketing-cloud#growthloop--marketing-cloud-use-cases) a GrowthLoop Audience with new customers.\n2. **Build Your GrowthLoop Journey:**\n \n 1. Navigate to Journeys:\n * In GrowthLoop, find the \"Journeys\" section.\n 2. Create a New Journey:\n * Select \"New Journey\" to start.\n 3. Define the Journey:\n * Set journey settings and save.\n * Select an entry audience of new customers from the last seven days.\n * Add a Destination Node for Marketing Cloud and configure export settings.\n 4. Publish the Journey:\n * Publish the journey to start immediately or schedule it.\n3. **Sending an Onboarding Email to the GrowthLoop Audience in Marketing Cloud:**\n \n 1. Navigate to Email Studio:\n * In Marketing Cloud, go to \"Email Studio.\"\n 2. Create a New Email:\n * Click on \"New Email\" to start your campaign.\n 3. Design Your Email Content:\n * Use the drag-and-drop editor or HTML to create your email content.\n 4. Select Your Audience:\n * Choose \"Data Extension\" as the send source.\n * Select the GrowthLoop audience segment exported from the Journey.\n 5. Set Up Sending Options:\n * Define the sender email address, subject line, and other sending options like tracking and reporting preferences.\n 6. Schedule or Send:\n * Choose to either schedule your email campaign for a later date or send it immediately.\n\nUnderstanding how customers engage with your marketing campaigns across different channels is essential for refining your strategy and enhancing targeting. That's why having all your performance data available in the Data Cloud for use in GrowthLoop audiences and journeys is invaluable. Now, with just a few clicks, you can seamlessly integrate your Salesforce Marketing Cloud data into your Data Cloud using the GrowthLoop Easy Button. Here’s how:\n\n![](https://files.readme.io/8c9c9c4-image.png)\n\n**Step-by-Step Breakdown**\n\n1. **Ingesting Marketing Cloud Interaction Data with Easy Button:**\n \n 1. In GrowthLoop, click on Ingest in left-hand menu.\n 2. Select \"Add Source\" in the upper right.\n 3. Select \"Salesforce Marketing Cloud.\"\n 4. Provide your credentials to access data in Marketing Cloud.\n 5. GrowthLoop will verify these credentials will work to begin pulling data.\n 6. Once setup, GrowthLoop will begin syncing data from Marketing Cloud to your Date Warehouse.\n2. **Using your Marketing Cloud Data in GrowthLoop Audiences:**\n \n 1. In GrowthLoop, click on \"Datasets\" in left-hand menu.\n 2. Select \"Add Dataset.\"\n 3. Select the Marketing cloud table you'd like to utilize when building an audience.\n 4. In Dataset Configuration, select the tables unique ID.\n 5. Save Dataset.\n 6. On \"Datasets\" page, select \"Dataset Groups\" tab.\n 7. Select the \"Dataset Group\" you' would like to add your Marketing Cloud dataset to use in audience and journey building.\n 8. Define join key between \"Dataset\" and the \"Primary Dataset\" in the Dataset Group.\n 9. Click “Save.”\n 10. Select \"Audiences\" in left-hand menu\n 11. Select \"New Audience\"\n 12. Select Dataset Group you just added Marketing Cloud Dataset to begin building your audience.\n 13. You can now see you can leverage your Marketing Cloud Dataset in building your audience in GrowthLoop and export to any paid media, crm, or marketing channel. You can use your Marketing Cloud dataset to design audiences that:\n 1. Haven't interacted with email in past 90 days\n 2. Opened a specific email more than once.\n 3. Interacted with a Content Card about a new product in your app.\n \n 1. Follow Steps i-xiii in the section above.\n 2. From GrowthLoop Home, select \"Journeys\" in left hand menu.\n 3. Select \"New Journey.\"\n 4. Insert your Journey Settings and click “Save.”\n 5. Drag a Criteria Node out onto the Journey Canvas.\n 6. Select “Settings” on Criteria Node Menu.\n 7. Add your Marketing Cloud dataset to the Criteria Node to use it as a criteria in your journey. For example, you can target:\n 1. Users in the journey who opened the email sent in previous step\n 2. Users in journey who haven't opened an email in 90 days, and send them to Facebook Ads.\n\nGrowthLoop was built to integrate seamlessly with Salesforce Marketing Cloud. We have many customers leveraging GrowthLoop audiences, syncs and journeys to get the best out of Salesforce Marketing cloud for their teams. If you are curious to learn more contact [support@growthloop.com](mailto:support@growthloop.com).\n\nUpdated 5 months ago\n\n* * *\n\n* [Salesforce Marketing Cloud](https://docs.growthloop.com/docs/salesforce-marketing-cloud)","2025-06-20T22:58:50.397Z","a3211ef3-037b-431d-9f1b-2c535a74cdef",[],[],{"_40":1113,"_128":1114,"_130":1115,"_132":1116,"_134":-5,"_13":-5,"_120":1117,"_122":136,"_25":1118,"_138":-5,"_139":1119,"_141":1120},"IP addresses: Which ones to whitelist | GrowthLoop Docs","ip-addresses-which-ones-to-whitelist-growthloop-docs","https://docs.growthloop.com/docs/ip-addresses","# IP addresses: Which ones to whitelist\n\nYou can allow access to the GrowthLoop platform by whitelisting only our outgoing IP addresses to your firewall rules.\n\n> 📘\n> \n> 34.69.50.194 \n> 35.226.252.61 \n> 34.121.106.121 \n> 35.239.73.167\n\n> 📘\n> \n> 34.159.89.36 \n> 35.246.129.9 \n> 34.159.126.6 \n> 34.159.99.133\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:32.796Z","514e7969-f10e-41b5-8e4b-3258260cb8ea",[],[],{"_40":1122,"_128":1123,"_130":1124,"_132":1125,"_134":-5,"_13":-5,"_120":1126,"_122":136,"_25":1127,"_138":-5,"_139":1128,"_141":1129},"Klaviyo","klaviyo-3","https://docs.growthloop.com/docs/klaviyo-sync","Klaviyo\nLearn how to create Syncs for Klaviyo\nLearn how to send the latest user info from your data warehouse to Klaviyo. This will enable you to build more accurate customer profiles for precise targeting. Let's get started!\nTo begin, sign into the GrowthLoop Platform and navigate to the Destinations tab on the left sidebar. Click New Destination in the top right corner.\n‍\nIn the Select Destination window that appears, just type Klaviyo into the search bar. Then, click Add Klaviyo.\nIn the window, please enter the following information to set up the connection to the destination.\nDestination Name: This is how the destination will be named and referred to in the app going forward.\nSync Frequency: Choose between Hourly or Daily to determine how frequently GrowthLoop exports audiences to Klaviyo.\nAPI Key: Locate your API key in account settings or create one using Create API KEY if it doesn't exist. Remember that only users with roles such as Owner, Admin, or Manager can view and create API keys.\nOnce you've entered the information, click on Create. We'll check to make sure we have all the necessary permissions to send audience data to Klaviyo. If everything is in order, you'll now find the new Klaviyo Destination in your list of connected destinations.\nTo route the latest user info (e.g., email, phone, city) to Klaviyo, go to the Signals tab on the left sidebar and click New Signal Route in the top right corner.\nClicking Create Signal Route will require you to select/insert the following information:\nRoute Name: A friendly name for the signal route.\nSync frequency: The default frequency for syncing the latest user info to a destination.\nUpdate Rule: The default operation for syncing the latest user info to a destination. Update only changes existing data, Insert only inserts new data, and Insert or update is a hybrid action that adds new data if it's not already present or updates it if it is.\nSource: The table that holds the latest user info. Usually, it's organized within a User table.\nMatch Field: The column used to match and identify users from your source table in the destination system.\nUnique Field: The column that contains values that are distinct for each user in the table.\nConnection: The destination you will sync data to. Please select Klaviyo.\nObject Type: The object that you want to send data to. Please select Identity.\nUnique Field: The column used to match and identify users from the destination system in your source table.\nOnce you finish selecting/inserting the required fields, click Save Route.\nIt's time to add the field mappings to activate your signal route. For Klaviyo integration, it's essential to map either Email or Phone, at the very least.\nTo map the field, select the column that represents the Email from the drop-down under Source.\n‍\nUnder the Destination section, select Email from the drop-down.\nIf you want to map more fields like Phone Number and City, simply click on Add Mapping. This will create a new row for Source > Destination, and then you can follow steps 5 and 6 again.\nFinally, click the toggle at the top of the page to enable the sync!\nCongratulations - you have successfully created a signal sync to Klaviyo!\nUpdated 3 months ago","2024-03-20T21:02:35.959Z","f95a68c1-c561-4ae1-89b9-f6ebac9f9f17",[],[],{"_40":1131,"_128":1132,"_130":1133,"_132":1134,"_134":-5,"_13":-5,"_120":1135,"_122":136,"_25":1136,"_138":-5,"_139":1137,"_141":1138},"Learn about journey state tables | GrowthLoop Docs","learn-about-journey-state-tables-growthloop-docs","https://docs.growthloop.com/docs/journey-state-tables","# Learn about journey state tables\n\n## Data Cloud Storage\n\nA quick overview of the information written back to your data warehouse for each journey.\n\nWhenever you publish a journey, a journey \"state table\" is written back to your data warehouse. This state table is maintained as a running record of each individual’s passage through the different steps of the journey.\n\n* Unlike snapshotting, in which multiple tables are written back to the data warehouse for each audience, there is only one state table written back for each journey\n* The journey state table is created within the same schema as your snapshotting tables\n* The naming convention for a journey state table is “journey\\_\\[journey id\\]”\n* The journey ID can be found in the GrowthLoop UI beneath the title of a journey\n* The state table is updated based on the journey run frequency configured as part of the journey settings\n\n| Field Name | Data Type | Description |\n| --- | --- | --- |\n| user\\_id | String | The unique identifier for an individual in your data |\n| created\\_at | Timestamp | Timestamp for when this record was created |\n| run\\_id | String | The ID for the specific run of the journey during which this record was created |\n| step\\_id | String | The ID of the node being evaluated (also available in the UI once the journey has been published) |\n| state | String | The state of this user for this step\\_id as part of this run\\_id. The possible values are **Completed**, **Pending**, and **Exited**. **Exited** indicates that the user was removed from the journey as a result of meeting global exit criteria identified as part of the journey settings. |\n| request\\_id | String | The ID for the request that triggered the node evaluation |\n| journey\\_id | String | The ID of the journey (also available in the UI beneath the journey title) |\n| glca\\_{custom attributes} | String | Any custom attributes that are created are stored with a prefix of \"glca\\_\" and the name of the custom attribute |\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:35.010Z","87533247-e61d-46fb-b9f2-adaa5719275a",[],[],{"_40":1140,"_128":1141,"_130":1142,"_132":1143,"_134":-5,"_13":-5,"_120":1144,"_122":136,"_25":1145,"_138":-5,"_139":1146,"_141":1147},"Learn how to integrate Iterable and GrowthLoop","learn-how-to-integrate-iterable-and-growthloop","https://docs.growthloop.com/docs/integrate-with-iterable","GrowthLoop and Iterable are two powerful platforms that, when used together, can help you create, manage, and optimize your campaigns with unparalleled precision. In this guide, we’ll walk you through how they can be used in tandem to enhance your marketing efforts, along with practical use cases and a step-by-step instructions to apply them.\n\n![](https://files.readme.io/fb69630-image.png)\n\nIterable is a robust marketing orchestration platform that empowers you to create personalized, cross-channel experiences at scale. While Iterable excels at crafting dynamic messages and journeys, it lacks access to trustworthy and comprehensive customer data. This leads to data silos and a fragmented customer view that impacts your ability to engage with customers and drive business results. This is where GrowthLoop steps in. GrowthLoop bridges the gap by connecting the most reliable data source, the Data Warehouse, directly with Iterable via a composable CDP. This enables you to:\n\n1. Create highly defined audiences based on various data points in your Data Warehouse.\n2. Export these segments directly to Iterable for targeted campaigns.\n3. Share customer segments between GrowthLoop and Iterable to ensure a unified view of the customer for commercial teams.\n4. Orchestrate cohesive, delightful journeys for your customers across email, SMS, push notifications, and paid media.\n5. Measure performance across different customer segments used in Iterable from a central location. With GrowthLoop's integration, marketers can optimize their campaigns with deeper insights and more targeted engagement strategies, driving better results and stronger customer relationships.\n\nUnlocking the power of your Data Warehouse with a composable CDP like GrowthLoop offers numerous ways to enhance customer experiences and marketing results. Here are some popular examples:\n\nGrowthLoop's Audience Builder offers marketers an effortless way to create audiences tailored for Iterable campaigns. Unlike solely relying on the limited data within Iterable, GrowthLoop taps into your organization’s complete Data Warehouse, incorporating data science predictions, internal records like coupon assignments, experiment labels, and more. Here's how it works:\n\n1. **Define Audiences:** Use GrowthLoop to build precise audience segments based on various data points in your Data Warehouse.\n2. **Export to Iterable:** Directly export these segments to Iterable as a static list for seamless integration.\n3. **Send Campaigns:** Utilize Iterable to send targeted email campaigns to these segments, ensuring your messaging reaches the right audience with ease.\n\n![](https://files.readme.io/e0be4b3-image.png)\n\n**Step-by-Step Breakdown**\n\n1. **Creating an Audience in GrowthLoop:**\n 1. Navigate to Audiences:\n 1. In the GrowthLoop app, on the left-hand side menu, click on \"Audience\".\n 2. Create a New Audience:\n 1. In the top right corner of the Central Audience Hub, click on \"New Audience\".\n 3. Define Your Audience Criteria:\n 1. Give your audience a descriptive name.\n 2. Utilize the builder to define your audience criteria. You can add filters based on various data points from your connected data sources.\n 3. _Example: Target users who have made a purchase in the last 3 months and live in California._\n 4. Refine Your Audience (Optional):\n 1. Use the \"Breakdown Report\" section to see a breakdown of your audience based on specific attributes.\n 2. Utilize \"Comparisons\" to compare your current audience with existing ones and potentially exclude overlapping segments.\n2. **Exporting an Audience to Iterable:**\n 1. Save and Export:\n 1. Once you're satisfied with your audience definition, click \"Save\" in the top right corner.\n 2. After saving, an \"Export Audience\" button will appear. Click this button.\n 2. Choose Export Destination:\n 1. Select \"Iterable\" as the export destination\n 2. Select the additional fields you would like to include in the export under “Personalization Fields.”\n 3. Export Confirmation:\n 1. Click \"Export\" to confirm and send your audience segment to Iterable. A static list will be created using the name of the audience.\n3. **Sending a Email Campaign in Iterable:**\n 1. Create a Campaign:\n 1. Click on the \"Messaging\" tab and select \"New Campaign\" to initiate a new campaign creation process.\n 2. Choose Campaign Type:\n 1. Select \"Email\" as the campaign type to create an email campaign.\n 3. Define Campaign Details:\n 1. Fill in the campaign name, label, and type. Choose whether to send a blast or a triggered campaign.\n 4. Select Audience:\n 1. In the \"Audience\" section, click “Select Lists” and choose the static list, containing the GrowthLoop audience.\n 5. Design Email Content\n 1. Proceed to the \"Content\" section to design the email content for your campaign. Use Iterable's built-in email editor to create visually appealing and engaging email content.\n 6. Preview and Test\n 1. Before sending the campaign, preview and test the email to ensure it appears correctly and functions as intended across different devices and email clients.\n 7. Schedule or Send:\n 1. Schedule your email campaign for a later date or send it immediately. To turn your one-off emails into ongoing campaigns, define a recurring export frequency in GrowthLoop. Options include \"Daily,\" \"Weekly,\" or a custom schedule based on your needs. This ensures your targeted audience segment is continuously updated in Iterable, capturing new records that meet your criteria.\n\nYou can use GrowthLoop audiences to trigger personalized journeys in Iterable. Here's how:\n\n1. **Create an Audience:** Use GrowthLoop to define your target audience based on data from your Data Warehouse.\n2. **Export the Audience:** Export this audience as a static list to Iterable.\n3. **Set Up Journey:** In Iterable, use this static list as the entry source in Journey Builder.\n4. **Launch Journey:** Start the journey to engage your audience through channels like email, SMS, and push notifications.\n\n![](https://files.readme.io/d5147ee-image.png)\n\n**Step-by-Step Breakdown**\n\n1. **Creating an Audience in GrowthLoop:**\n 1. [Create](https://docs.growthloop.com/docs/integrate-with-iterable#growthloop--iterable-use-cases) a GrowthLoop Audience.\n2. **Exporting an Audience to Iterable:**\n 1. [Export](https://docs.growthloop.com/docs/integrate-with-iterable#growthloop--iterable-use-cases) the GrowthLoop Audience as a static list to Iterable.\n3. **Create an Iterable Journey and target your GrowthLoop Audience:**\n 1. Open Journey Builder:\n 1. Navigate to the \"Journey\" tab on the main navigation menu.\n 2. Click on \"Create Journey\" to start building a new journey.\n 2. Name and Configure Your Journey:\n 1. Provide a name and description for your journey to help you identify it later.\n 3. Select Entry Source:\n 1. Choose \"Subscribe to List\" as the entry source for your journey.\n 2. From the dropdown menu, select the static list you created or imported earlier.\n 4. Define Journey Steps:\n 1. Add steps to your journey based on how you want to engage with your audience. Here are some common steps:\n 1. **Send Email:** Drag and drop the \"Send Email\" action into your journey canvas. Configure the email content and settings.\n 2. **Send SMS:** Drag and drop the \"Send SMS\" action. Configure the SMS content and settings.\n 3. **Push Notification:** Drag and drop the \"Push Notification\" action. Configure the notification content and settings.\n 4. **Wait Time:** Use the \"Wait\" action to set delays between actions.\n 5. Set Conditions and Triggers:\n 1. Use conditions and triggers to personalize the journey based on subscriber interactions. For example:\n 1. **Condition Split:** Add a condition split to branch the journey based on user behavior (e.g., email opened, link clicked).\n 2. **Trigger:** Use triggers to initiate actions based on real-time events (e.g., product purchase, form submission).\n 6. Activate the Journey:\n 1. Once you are satisfied with the setup, click on the \"Activate\" button to start the journey.\n 2. Congratulations! You've successfully executed an Iterable Journey to a GrowthLoop audience. If you choose to set the audience as a recurring export in GrowthLoop, contacts will be added to the static list and will continue to enter the journey on an ongoing basis.\n\nPersonalizing your campaigns is key to capturing attention and driving engagement. When you customize messages based on individual preferences, customers are more likely to engage, make purchases, and stay loyal. Thanks to GrowthLoop, you can easily achieve that by bringing in user attributes from your Data Warehouse to Iterable with Syncs, helping you create highly targeted and successful marketing campaigns. Here's how:\n\n1. **Create Your Sync in GrowthLoop:** Build a sync that routes user attributes from your Data Warehouse to existing profiles in Iterable.\n2. **Craft Your Email in Iterable**: Design your email and include user attributes as personalization strings with handlebars such as: {{fieldName}}.\n3. **Schedule or Send:** Schedule your personalized email campaign or send it immediately.\n\n![](https://files.readme.io/4f0469b-image.png)\n\n**Step-by-Step Breakdown**\n\n1. **Creating a Sync in GrowthLoop:**\n 1. Click [here](https://docs.growthloop.com/docs/iterable-sync) to see an in-depth guide on how to set up Syncs from your Data Warehouse to Iterable.\n2. **Leveraging User Attributes in Iterable Campaigns:**\n 1. Create a Campaign:\n 1. Click on the \"Messaging\" tab and select \"New Campaign\" to initiate a new campaign creation process.\n 2. Choose Campaign Type:\n 1. Select \"Email\" as the campaign type to create an email campaign.\n 3. Define Campaign Details:\n 1. Fill in the campaign name, label, and type. Choose whether to send a blast or a triggered campaign.\n 4. Select Audience:\n 1. In the \"Audience\" section, click “Select Lists” and choose the static list, containing records you’ve updated with new attributes from the Data Warehouse.\n 5. Design Email Content\n 1. Proceed to the \"Content\" section to design the email content for your campaign. Use Iterable's built-in email editor to create visually appealing and engaging email content.\n 6. Insert Personalization Strings:\n 1. Enclose the name of your desired event or user profile field in double curly braces like this: {{fieldName}}.\n 2. Iterable will automatically replace these placeholders with the corresponding data from each user’s profile in the email template.\n 7. Schedule or Send:\n 1. Schedule your email campaign for a later date or send it immediately.\n\nEvents, like user attributes, are essential for creating targeted and successful marketing campaigns. Events track actions users take, such as visiting a product page, clicking an email, or downloading an app. These actions map a user's journey and are vital for crafting personalized customer experiences. Here’s how to use these events as personalization fields in your email templates:\n\n1. **Create Your Sync in GrowthLoop:** Build a sync that routes events from your Data Warehouse to existing profiles in Iterable.\n2. **Craft Your Email in Iterable**: Design your email and include events as personalization strings with handlebars such as: {{storeOrder}}.\n3. **Schedule or Send:** Schedule your personalized email campaign or send it immediately.\n\n![](https://files.readme.io/18d9dde-image.png)\n\n**Step-by-Step Breakdown**\n\n1. **Creating a Sync in GrowthLoop:**\n 1. Click [here](https://docs.growthloop.com/docs/iterable-sync) to see an in-depth guide on how to set up Syncs from your Data Warehouse to Iterable.\n2. **Leveraging custom and standard events in Iterable Campaigns:**\n 1. Create a Campaign:\n 1. Click on the \"Messaging\" tab and select \"New Campaign\" to initiate a new campaign creation process.\n 2. Choose Campaign Type:\n 1. Select \"Email\" as the campaign type to create an email campaign.\n 3. Define Campaign Details:\n 1. Fill in the campaign name, label, and type. Choose whether to send a blast or a triggered campaign.\n 4. Select Audience:\n 1. In the \"Audience\" section, click “Select Lists” and choose the static list, containing records you’ve updated with events from the Data Warehouse.\n 5. Design Email Content\n 1. Proceed to the \"Content\" section to design the email content for your campaign. Use Iterable's built-in email editor to create visually appealing and engaging email content.\n 6. Insert Personalization Strings:\n 1. Enclose the name of your desired event or user profile field in double curly braces like this: {{storeOrder}}.\n 2. Iterable will automatically replace these placeholders with the corresponding data from each user’s profile in the email template.\n 7. Schedule or Send:\n 1. Schedule your email campaign for a later date or send it immediately.\n\nGrowthLoop Journeys automates personalized customer journeys across channels from your Data Warehouse. Using GrowthLoop's Journey Builder, marketers can orchestrate journeys across 100+ destinations alongside Iterable, access organizational data, use data science predictions, and gain visibility for analysis. Here's how to create a basic journey to export new customers for onboarding emails:\n\n1. **Create an Audience:** Define your target audience in GrowthLoop using various data points, such as new customer acquisitions.\n2. **Build the Journey:** In GrowthLoop, navigate to the Journeys section and create a new journey.\n3. **Configure and Export:** Set the journey's entry audience to newly acquired customers, add a Destination Node, and configure it to export the audience to Iterable as a static list.\n4. **Send Onboarding Emails:** In Iterable, use the static list as the audience for your onboarding email campaign. Design and send personalized welcome emails to engage your new customers.\n\n![](https://files.readme.io/2b91c5b-image.png)\n\nBefore we walk through how this setup works, there are several key benefits to having your journeys live in a Composable CDP.\n\n* **Unified Marketing Channels:** Craft journeys across **many different marketing channels**, not just what Iterable supports today. This lets you reach your audience in all the places they hang out online.\n* **Data-Driven Decisions:** Use **all your company's data**, like surveys, purchase history, and even predictions from your data scientists, to personalize each step of your journey. This ensures your messages are relevant and timely.\n* **Enhanced Collaboration:** **Data teams can see exactly what journeys are running** and how users interact with them. This allows for better collaboration between marketing and data teams for optimal campaign performance.\n* **Global Flexibility:** **Different regions can use their preferred marketing tools**, while still leveraging the same journey builder in GrowthLoop. This provides flexibility without sacrificing consistency.\n* **Avoid Vendor Lock-in:** **You're not locked into a single marketing tool.** GrowthLoop lets you easily switch marketing tools if needed, and you always own your data.\n\n**Step-by-Step Breakdown**\n\n1. **Define Your Target Audience in GrowthLoop:**\n 1. [Create](https://docs.growthloop.com/docs/integrate-with-iterable#growthloop--iterable-use-cases) a GrowthLoop Audience with new customers.\n2. **Build Your GrowthLoop Journey:**\n 1. Navigate to Journeys:\n 1. In GrowthLoop, find the \"Journeys\" section.\n 2. Create a New Journey:\n 1. Select \"New Journey\" to start.\n 3. Define the Journey:\n 1. Set journey settings and save.\n 2. Select an entry audience of new customers from the last seven days.\n 3. Add a Destination Node for Iterable and configure export settings.\n 4. Publish the Journey:\n 1. Publish the journey to start immediately or schedule it.\n3. **Sending an Onboarding Email to the GrowthLoop Audience in Iterable:**\n 1. Create a Campaign:\n 1. Click on the \"Messaging\" tab and select \"New Campaign\" to initiate a new campaign creation process.\n 2. Choose Campaign Type:\n 1. Select \"Email\" as the campaign type to create an email campaign.\n 3. Define Campaign Details:\n 1. Fill in the campaign name, label, and type. Choose whether to send a blast or a triggered campaign.\n 4. Select Audience:\n 1. In the \"Audience\" section, click “Select Lists” and choose the static list, containing the GrowthLoop audience.\n 5. Design Email Content\n 1. Proceed to the \"Content\" section to design the email content for your campaign. Use Iterable's built-in email editor to create visually appealing and engaging email content.\n 6. Schedule or Send:\n 1. Schedule your email campaign for a later date or send it immediately. To turn your one-off emails into ongoing campaigns, define a recurring export frequency in GrowthLoop. Options include \"Daily,\" \"Weekly,\" or a custom schedule based on your needs. This ensures your targeted audience segment is continuously updated in Iterable, capturing new records that meet your criteria.\n\nUnderstanding how customers engage with your marketing campaigns across different channels is essential for refining your strategy and enhancing targeting. That's why having all your performance data available in the Data Warehouse for use in GrowthLoop audiences and journeys is invaluable. Now, with just a few clicks, you can seamlessly integrate your Iterable data into your Data Warehouse using the GrowthLoop Easy Button. Here’s how:\n\n![](https://files.readme.io/578a6a4-image.png)\n\n**Step-by-Step Breakdown**\n\n1. **Ingesting Iterable Interaction Data with Easy Button:**\n \n 1. In GrowthLoop, click on Ingest in the left-hand menu.\n 2. Select \"Add Source\" in the upper right.\n 3. Select \"Iterable.\"\n 4. Provide your credentials to access data in Iterable.\n 5. GrowthLoop will verify these credentials will work to begin pulling data.\n 6. Once set up, GrowthLoop will begin syncing data from Iterable to your Data Warehouse.\n2. **Using your Iterable Data in GrowthLoop Audiences:**\n \n 1. In GrowthLoop, click on \"Datasets\" in the left-hand menu.\n 2. Select \"Add Dataset.\"\n 3. Select the Iterable table you'd like to utilize when building an audience.\n 4. In Dataset Configuration, select the table's unique ID.\n 5. Save Dataset.\n 6. On the \"Datasets\" page, select the \"Dataset Groups\" tab.\n 7. Select the \"Dataset Group\" you would like to add your Iterable dataset to use in audience and journey building.\n 8. Define the join key between the \"Dataset\" and the \"Primary Dataset\" in the Dataset Group.\n 9. Click “Save.”\n 10. Select \"Audiences\" in the left-hand menu\n 11. Select \"New Audience\"\n 12. Select the Dataset Group you just added to your Iterable Dataset to begin building your audience.\n 13. You can now see you can leverage your Iterable Dataset in building your audience in GrowthLoop and export to any paid media, crm, or marketing channel. You can use your Iterable dataset to design audiences that:\n 1. Haven't interacted with email in the past 90 days\n 2. Opened a specific email more than once.\n 3. Interacted with a Content Card about a new product in your app.\n \n 1. Follow Steps i-xiii in the section above.\n 2. From GrowthLoop Home, select \"Journeys\" in the left-hand menu.\n 3. Select \"New Journey.\"\n 4. Insert your Journey Settings and click “Save.”\n 5. Drag a Criteria Node out onto the Journey Canvas.\n 6. Select “Settings” on the Criteria Node Menu.\n 7. Add your Iterable dataset to the Criteria Node to use it as a criterion in your journey. For example, you can target:\n 1. Users in the journey who opened the email sent in the previous step\n 2. Users in the journey who haven't opened an email in 90 days, and send them to Facebook Ads.\n\nGrowthLoop was built to integrate seamlessly with Iterable. We have many customers leveraging GrowthLoop audiences, syncs and journeys to get the best out of Iterable for their teams. If you are curious to learn more contact [support@growthloop.com](mailto:support@growthloop.com).\n\nUpdated 5 months ago\n\n* * *","2025-06-20T22:58:54.019Z","cd4f66c6-c18a-4536-855c-50c94069c708",[],[],{"_40":1149,"_128":1150,"_130":1151,"_132":1152,"_134":-5,"_13":-5,"_120":1153,"_122":136,"_25":1154,"_138":-5,"_139":1155,"_141":1156},"Leverage customer data from BigQuery | GrowthLoop Docs","leverage-customer-data-from-bigquery-growthloop-docs","https://docs.growthloop.com/docs/bigquery","# Leverage customer data from BigQuery\n\n## Google BigQuery\n\nLearn how to set up BigQuery source connection\n\nThe GrowthLoop Audience Builder Application connects directly to BigQuery so you can leverage the customer data in your data warehouse to create audiences with just a few clicks. \n‍ \nTo establish the connection to BigQuery, here are the key steps we will walk through together.\n\n1. Create a GCP Service Account\n2. Configure GCP Permissions\n3. Create a BQ dataset to store snapshots\n4. Connect your BigQuery to the GrowthLoop App\n\nThe first step is to create a service account in the GCP project where your customer data lives. Navigate to the project where your customer data is, and click on **IAM & Admin** in the panel on the left.\n\n![](https://files.readme.io/2239266-Untitled.png)\n\nClick **Service Accounts**.\n\n![](https://files.readme.io/e7d4ab3-Untitled_1.png)\n\nCreate a new Service Account by entering\n\n* Service account name - often company\\_name-flywheel\n* Service account ID - make sure you save this account ID. You will need it later.\n* Service account description\n\nClick **Create and Continue**\n\n![](https://files.readme.io/13efa51-Untitled_2.png)\n\nNext grant the service account three roles at the Project level:\n\n* BigQuery User\n* BigQuery ReadSession User\n* BigQuery Metadata Viewer\n\nContinue to step three. Leave the **Service account user role** and **Service account admins role** fields blank and click **Done**.\n\n![](https://files.readme.io/5e71fd7-Untitled_3.png)\n\nNavigate to the **Keys** tab and click **Add Key**.\n\n![](https://files.readme.io/41e8358-Untitled_4.png)\n\nClick **Create new key**. Make sure that the **JSON** key type is selected and click **Create**. A JSON file will download to your computer. Save it in a location that can be easily found for later.\n\n![](https://files.readme.io/d794aaf-Untitled_5.png)\n\nYou have now created a new Service Account and provided permissions to the GCP project that houses your customer data.\n\nWithin your GCP project, navigate to the datasets that you want to connect to the app. Keep in mind that right now, all tables you are looking to join together into a dataset group need to be in the same dataset. However, you can connect tables from different datasets, as long as the joins exist within the same dataset, and the service account has permissions for each dataset they are looking to connect in the app.\n\nNow we are going to provide read access to the datasets for the Service Account. Click on the three vertical bubbles next to a dataset that you want to connect to the application.\n\n![](https://files.readme.io/d15b461-Untitled_6.png)\n\nClick **Share**. Add a new principal with the permission **BigQuery Data Viewer** and save. At this point, you should have a service account with four sets of permissions:\n\n* BigQuery User at the project level\n* BigQuery ReadSession User at the project level\n* BigQuery Metadata Viewer at the project level\n* BigQuery Data Viewer at the dataset level\n\nWithin the GCP project that houses your data, create a new dataset called **flywheel\\_system**. This dataset will store the snapshots created during audience exports. Grant your service account Data Owner permissions by clicking on the three vertical bubbles next to the dataset name. Click **Share**. Add a new principal with the permission **BigQuery Data Owner** and save. Now you have the flywheel\\_system dataset with the necessary permissions to write snapshots to BigQuery.\n\nFirst, navigate to the link to the application the GrowthLoop team has provided you. If we haven’t provided a link, please reach out to the solutions architect for your project.\n\nWhen you click on the link, you will be brought to the signup page. Enter your company credentials and click **Sign Up**.\n\nEnter your **Organization name** and **Industry**. Click the checkbox to agree to the terms and then **Continue**.\n\n![](https://files.readme.io/120f14c-Untitled_7.png)\n\nSelect BigQuery as the data warehouse you wish to connect to. Click **Upload file** and navigate to where your service account key is located on your computer. Upload the file to the application and you will see **Success** appear. If you are having issues verifying your service account, please reach out to [solutions@flywheelsoftware.com](mailto:solutions@flywheelsoftware.com) or your solutions architect for support.\n\n![](https://files.readme.io/f837d8b-Untitled_8.png)\n\nNext, we are going to connect the applications to specific datasets in your data warehouse. Select the **Dataset** that you wish to connect to. All of your data that you want to bring in to the application must live in the dataset(s) you provided Data Viewer permissions to. Then, select the **Table** that you’d like to connect to within your dataset. Often, new users connect their Customer data table first. Later on you are also able to connect more tables that you wish to use in your analysis in the application.\n\n![](https://files.readme.io/5cb4b28-Untitled_9.png)\n\nNext, we want to define our table configurations.\n\n1. Select the field that contains the unique id for your table. This will often be a customer id for customer data.\n2. Select a device id. This field is only important to define correctly if you plan on exporting audiences to a destination that requires device ids, like TikTok.\n3. Check the fields that you want to see automatically when you start to build a new audience. This configuration can be tweaked later, but common selections are a state or a date field.\n\n![](https://files.readme.io/7794856-Untitled_10.png)\n\nClick **Next**. Now you’re all set up and ready to build your first audiences!\n\n![](https://files.readme.io/5cae9e1-Untitled_11.png)\n\nUpdated 5 months ago\n\n* * *\n\n* [Create an Audience](https://docs.growthloop.com/docs/create-an-audience)","2024-03-20T21:02:21.837Z","c8287ee7-42b5-486a-92bc-b91e6aab4799",[],[],{"_40":1158,"_128":1159,"_130":1160,"_132":1161,"_134":-5,"_13":-5,"_120":1162,"_122":136,"_25":1163,"_138":-5,"_139":1164,"_141":1165},"Leverage customer data from Databricks | GrowthLoop Docs","leverage-customer-data-from-databricks-growthloop-docs","https://docs.growthloop.com/docs/databricks","# Leverage customer data from Databricks\n\nGrowthLoop Audience Platform connects directly to Databricks so you can leverage the customer data in your data lake to create audiences with just a few clicks.\n\nTo establish the connection to Databricks, here are the key steps we will walk through together.\n\n1. Creating a Private Access Token (PAT) or OAuth Service Principle\n2. Finding your connection metadata\n3. Providing your connection metadata and private access token to the GrowthLoop app\n\nNavigate to the User Management tab of your Databricks account console.\n\nNavigate to the Service Principles tab.\n\n![](https://files.readme.io/b915fa9e0baa84211380ac6d29095b9eeb4fd3e674fc334a3afeadc27638f7ac-Screenshot_2024-10-22_at_10.31.07_AM.png)\n\nClick the \"Add a Service Principle\" button on the right.\n\nGive it a name and click the \"Create\" button.\n\nClick on the service principle to open the Service Principle details page.\n\nClick \"Generate Secret\" at the bottom.\n\n![](https://files.readme.io/66815b2e9fb3cced6dc56ed4bd1dcac4064ee68135bd3ad0e690df9e44146412-Screenshot_2024-10-22_at_10.37.46_AM.png)\n\nCopy the Client ID and Client Secret pair before closing the modal.\n\nNavigate to your Databricks workspace before proceeding to the section on \"Finding Your Connection Metadata\"\n\n![](https://files.readme.io/328ecd4588c8ea5bc57cf46f3146c2e554ba917d50ee0a67e37b96ec6ffcb2b6-Screenshot_2024-10-22_at_10.41.33_AM.png)\n\nNavigate to the Admin Settings page in the top right of your Databricks console.\n\n![](https://files.readme.io/97d9891-navigate-to-admin.png)\n\nNavigate to the Developer tab and click **manage** on **Access tokens**\n\n![](https://files.readme.io/318f080-developer-tab.jpg)\n\nHit the **Generate** button to create a new token and copy it in a file as we'll need this later on.\n\n![](https://files.readme.io/cbedc3f-generate-new-token.png)\n\nNavigate to **SQL Warehouses** in your workspace and select the warehouse you'd like to connect to.\n\n![](https://files.readme.io/f8bf11a-Screenshot_2024-01-24_at_4.15.23_PM.png)\n\nNavigate to the **Connection details** tab and copy both\n\n* **Server hostname**\n* and **HTTP path**\n\nwhich we'll use in the next step.\n\nMake sure you click the **Start** button in the top-right in case your Databricks warehouse is not running.\n\n![](https://files.readme.io/593b6ea-connection-details.png)\n\nOnce you log into your GrowthLoop account, provide the industry you belong to and agree to the terms & conditions to move ahead.\n\n![](https://files.readme.io/a8d1e7c-image.png)\n\nPick **Databricks** as your data warehouse\n\n![](https://files.readme.io/5433237eb9089ce1a56196c78244f435426402d9bf4ad143bf9403023f0b18a0-Screenshot_2024-10-28_at_10.22.28_AM.png)\n\nProvide the following details:\n\n* **Name** -- Anything you'd like to call this source connection\n* **Description** -- Details on the source connection\n* **Catalog** -- The name of the catalog in Databricks that you want to connect to by default\n* **Hostname** -- Copied previous step\n* **HTTP Path** -- Copied previous step\n* **Client ID** -- Copied previous step for option 1\n* **Client Secret** -- Copied previous step for option 1\n* **Access Token** -- Copied previous step for option 2\n* **Dataset for snapshots** -- The desired schema for storing application state - \"flywheel\\_system\" recommended\n\n**Note** -- If your connection failed in the first try (after a few minutes), give it one more try before you contact our team. This is usually because the first attempt tries to wake up your Databricks warehouse.\n\n![](https://files.readme.io/d25ac9b-image.png)\n\nYou're now ready to build your first dataset in GrowthLoop.\n\nTry choosing your Dataset and Table from the drop-downs and give your Table alias & description some details, while defining your unique key.\n\nYou can choose which fields from your data you'd like to always be available when building any future audiences from this dataset (eg, total\\_credit\\_amount)\n\n![](https://files.readme.io/3d40c64-image.png)\n\nOn the next step you should provide the **retention** as well as **catalog** to store your audience snapshots at.\n\n![](https://files.readme.io/7108134-Screenshot_2024-01-24_at_12.29.02_PM.png)\n\nYou're all set up to build your first audience now:\n\n![](https://files.readme.io/4bd5ac9-image.png)","2024-03-20T21:02:22.092Z","f324490c-a470-4be0-ba0d-9cf61302132f",[],[],{"_40":1167,"_128":1168,"_130":1169,"_132":1170,"_134":-5,"_13":-5,"_120":1171,"_122":136,"_25":1172,"_138":-5,"_139":1173,"_141":1174},"Leverage customer data from Redshift | GrowthLoop Docs","leverage-customer-data-from-redshift-growthloop-docs","https://docs.growthloop.com/docs/redshift","# Leverage customer data from Redshift\n\n## Amazon Redshift\n\nLearn how to set up a Amazon Redshift source connection\n\n1. Access to an AWS account and Amazon Redshift cluster\n2. The user has an admin role to access the Amazon Redshift cluster. This user must also have created schema privileges.\n3. Add the IP of GrowthLoop’s NAT in your Amazon Redshift Security Groups so that the web app can reach your Amazon Redshift instances. Reach out to [support@growthloop.com](mailto:support@growthloop.com) for the IP address.\n4. The Amazon Redshift cluster must be spun up and connected to a database. Click **Connect to the database**. If a database is not connected to Amazon Redshift, the status will be blank and you need to click **Change connection** to connect to your database.\n\nIf the database is connected to Amazon Redshift, you will see the status **Connected**.\n\n![](https://files.readme.io/237fda5-Untitled.png)\n\n1. Create schema flywheel\\_system in the Amazon Redshift cluster’s database. In the query editor, paste and run this command: `create schema flywheel_system`\n2. If you will be using Signal Routing, run this command in the Amazon Redshift cluster’s query editor: `create schema signal_snapshots` See `` for more information on signal routing with GrowthLoop.\n3. Amazon Redshift clusters must be publicly accessible. You can make that change in the Amazon Redshift UI. Select the cluster, click **Actions**, and **Modify publicly accessible setting**. Select **Enable** in the popup and **Save changes**.\n\n![](https://files.readme.io/a13e160-Untitled_1.png) ![](https://files.readme.io/06f0ce7-Untitled_2.png)\n\n1. [Visit the GrowthLoop application](https://app.flywheelsoftware.com/audiences). If you were provided with a different application URL, use that.\n2. Sign up using your company credentials.\n3. If necessary, verify your email by clicking the verify link in the email sent to your email address.\n4. Return to the application and enter your **Organization name** and **Industry**. Click the checkbox to agree to the terms and then **Continue**.\n\n![](https://files.readme.io/cd732cc-Untitled_3.png)\n\n1. Select Amazon Redshift as the data warehouse you wish to connect to.\n\n![](https://files.readme.io/309d479-Untitled_5.png)\n\n1. Next, enter the required information to connect to Amazon Redshift:\n 1. **Name**: name the connection to your data warehouse. This is somewhat arbitrary.\n 2. **Description**: description of the connection to your data warehouse. This is somewhat arbitrary.\n 3. **Amazon Redshift username**: username for the user that allows access to the Amazon Redshift cluster where your data is stored. This can be found on the Amazon Redshift cluster UI’s Properties tab, or in the Query Editor when it is connected to your database.\n 4. **Amazon Redshift password**: admin user password for the user that allows access to the Amazon Redshift cluster where your data is stored. You can change the admin user password in the Amazon Redshift cluster UI’s Properties tab if necessary\n 5. **Database**: name of the database that you want to connect to the app.\n 6. **Schema**: name of schema for the table you want to connect to the app. For example, If you are looking to connect your user table to the app, select the user schema.\n 7. **Host**: Database endpoint, without the port and database name.\n 1. Copy the cluster endpoint. It should look have this format: **:/**\n 2. Remove the port and database name, leaving just the host\n 1. Example: r edshift-cluster-testname0123.us-east-1.redshift.amazonaws.com\n 3. Enter the edited host as the host in the app\n 8. **Port:** Open the port to access the database. The port can be found in the Amazon Redshift cluster UI’s Properties tab, or as part of the database endpoint. The format of the endpoint is **:/**\n\n![](https://files.readme.io/df7b114-Untitled_6.png)\n\n1. Select the dataset you wish to connect to the app.\n\n![](https://files.readme.io/fa2a893-Untitled_6.png)\n\n1. Select a table you want to connect to. You can add more tables later, as well.\n\n![](https://files.readme.io/40242c0-Untitled_7.png)\n\n1. Add table alias and description\n\n![](https://files.readme.io/b0e87ab-Untitled_8.png)\n\n1. Select the unique key, which uniquely identifies a database record.\n\n![](https://files.readme.io/cd57816-Untitled_9.png)\n\n1. If required, select a device ID. The device ID is often used to target an individual during a marketing campaign, so it will be necessary to define the device ID before sending any data to a marketing destination.\n\n![](https://files.readme.io/4b110b8-Untitled_10.png)\n\n1. Select fields that you would like to see by default in the app when you create a new audience. Additional fields will be available in the app to manually add to an audience. Default settings can be edited at any time in the app.\n\n![](https://files.readme.io/4c559ef-Untitled_11.png)\n\n1. You have successfully connected your Amazon Redshift database to the app!\n\n![](https://files.readme.io/ac45cf1-Untitled_12.png)\n\nAWS recommends that customers create separate queues for monitoring database queries. Instructions for setting up these queries can be found at [this link](https://docs.aws.amazon.com/redshift/latest/dg/cm-c-defining-query-queues.html).\n\nUpdated 5 months ago\n\n* * *\n\n* [Setup Datasets](https://docs.growthloop.com/docs/setup-datasets)\n* [Setup Dataset Groups](https://docs.growthloop.com/docs/setup-dataset-group)\n* [Create an Audience](https://docs.growthloop.com/docs/create-an-audience)","2024-03-20T21:02:21.309Z","8374ce6b-350a-4dcb-8b77-c445c59cbe50",[],[],{"_40":1176,"_128":1177,"_130":1178,"_132":1179,"_134":-5,"_13":-5,"_120":1180,"_122":136,"_25":1181,"_138":-5,"_139":1182,"_141":1183},"Leverage customer data from Snowflake | GrowthLoop Docs","leverage-customer-data-from-snowflake-growthloop-docs","https://docs.growthloop.com/docs/snowflake","# Leverage customer data from Snowflake\n\nLearn how to setup Snowflake source connection\n\nIn this article, we’ll walk you through how to connect your Snowflake account to GrowthLoop, so you can easily use the customer data in your cloud warehouse to build and activate audiences.\n\n**Snowflake** is a cloud-based data platform that allows organizations to store, manage, and analyze large volumes of data with high performance and flexibility. It supports a wide range of data workloads - including data warehousing, data lakes, and machine learning - enabling teams to easily share and collaborate on data across business units.\n\nBefore connecting Snowflake to GrowthLoop, make sure to complete the following steps:\n\n1. **Generate a public/private key pair** to authenticate your Snowflake user.\n2. **Create a Snowflake user and role** with the appropriate permissions for data access.\n3. **Set up a dedicated Snowflake schema and storage integration** named `FLYWHEEL_APP_GCP` for audience exports.\n\n> ❗️\n> \n> The storage integration must be named `FLYWHEEL_APP_GCP`. If it is named anything else, the connection will not work.\n\n1. Open your local machine’s command prompt or terminal and run the following command:\n\n```\nopenssl genrsa 2048 | openssl pkcs8 -topk8 -inform PEM -out fw_private_key.p8\n```\n\n2. After running this command, you will be prompted for an encryption password. Please enter any secure password and keep record of this for later use. Then run the following command:\n\n```\nopenssl rsa -in fw_private_key.p8 -pubout -out fw_pub_key.pub\n```\n\n3. After running this command, you will be prompted for the encryption password set above. Please enter the encryption password and take note of where your public and private key are stored for later use.\n\n4. Login to your Snowflake account with a user who is assigned administrative privileges to manage users and roles. A common admin role with the necessary privileges is `ACCOUNTADMIN` or `SECURITYADMIN`.\n5. Then, open a worksheet and run the following commands:\n\n**Create a Role**\n\n```\nuse role <*INPUT_ROLE>*;\n\ncreate role <*fw_access_role_name*>;\n```\n\n> 📘\n> \n> If you encounter any permission errors, ensure that you have a properly permissioned role selected in your Snowflake worksheet (pictured in the top right corner of the image below).\n> \n> ![](https://files.readme.io/ce8af85-Untitled.png)\n\n> ❗️\n> \n> If running multiple commands ensure the “**All Queries**” box is checked.\n> \n> ![](https://files.readme.io/aef07bf-Untitled_1.png)\n\n7. Next, Assign Privileges to the Role.\n\n```\nuse role <*INPUT_ROLE>*;\n\ngrant usage on warehouse COMPUTE_WH to role <*fw_access_role_name*>;\n\ngrant usage on database CUSTOMER_DATA_MODEL to role <*fw_access_role_name*>;\n\ngrant usage on all schemas in database CUSTOMER_DATA_MODEL to role <*fw_access_role_name*>;\n\ngrant select on all tables in database CUSTOMER_DATA_MODEL to role <*fw_access_role_name*>;\n\ngrant select on all views in database CUSTOMER_DATA_MODEL to role <*fw_access_role_name*>;\n\ngrant usage on future schemas in database CUSTOMER_DATA_MODEL to role <*fw_access_role_name*>;\n\ngrant select on future tables in database CUSTOMER_DATA_MODEL to role <*fw_access_role_name*>;\n\ngrant select on future views in database CUSTOMER_DATA_MODEL to role <*fw_access_role_name*>;\n\n//Replace COMPUTE_WH with the name of your data warehouse\n//Replace fw_access_role with the name of the role created in the 'Create a Role' step above\n//Replace CUSTOMER_DATA_MODEL with the name of the database to be connected to GrowthLoop \n```\n\n8. Then, Create a **User** and Assign a **Role**.\n\n```\nuse role <*INPUT_ROLE*>;\n\ncreate user flywheel_service_user password='abc123' default_role = <*fw_access_role_name*> default_warehouse = COMPUTE_WH default_namespace = CUSTOMER_DATA_MODEL;\n\ngrant role <*fw_access_role_name*> to user flywheel_service_user;\n```\n\n9. Lastly, Assign **Public Key** to `flywheel_service_user`.\n\n```\nuse role <*INPUT_ROLE*>;\n\nalter user flywheel_service_user set rsa_public_key='MIIBIjANBgkqh...';\n\n//the rsa_public_key value can be found in the fw_pub_key.pub file created above. Exclude the '------BEGIN PUBLIC KEY------' and '-----END PUBLIC KEY-----' header and footer in this value.\n```\n\nBefore exporting audiences, a schema must be established for GrowthLoop to write snapshotting tables. Snapshotting tables will store changes in audience, and sync membership over time. These tables are necessary to maintain ongoing syncs to your destinations.\n\n10. In the same database where you connected your customer data, create the `FLYWHEEL_SYSTEM` schema.\n\n> 📘\n> \n> You may choose any alternative name that you prefer for this schema.\n\n11. Create a **New Schema**.\n\n```\ncreate schema FLYWHEEL_SYSTEM;\n```\n\n12. Grant Privileges to `FLYWHEEL_SYSTEM` schema.\n\n```\ngrant all on schema FLYWHEEL_SYSTEM to role fw_access_role;\n//Replace fw_access_role with the name of the role created in the 'Create a Role' step\n```\n\n13. Create **Storage Integration**.\n\n> 📘\n> \n> Snowflake storage integration allows GrowthLoop to export data to your marketing platforms. This data is exported and deleted after it’s been exported and not stored on the GrowthLoop system. To utilize a GrowthLoop managed bucket, please follow the steps below. To configure your own cloud storage bucket for exports please check out [Setup External Storage in GrowthLoop](https://docs.growthloop.com/docs/bring-your-own-bucket#setup-external-storage-in-growthloop)\n\n**For SaaS**\n\n14. Create a new storage integration in your Snowflake instance to allow writing to temporary bucket to enable exporting. Below are examples for Google Cloud and AWS.\n\n_Google Cloud_\n\n```\ncreate storage integration flywheel_app_gcp\n type = external_stage\n storage_provider = gcs\n enabled = true\n storage_allowed_locations = ('gcs://flywheel-prod-328213-outgoing/exports/');\n```\n\n15. You’ll need to provide GrowthLoop with either the `STORAGE_GCP_SERVICE_ACCOUNT` property. To access these properties, run the `DESC STORAGE INTEGRATION` command in Snowflake.\n\n```\nDESC STORAGE INTEGRATION flywheel_app_gcp;\n\n+-----------------------------+---------------+-----------------------------------------------------------------------------+------------------+\n| property | property_type | property_value | property_default |\n+-----------------------------+---------------+-----------------------------------------------------------------------------+------------------|\n| ENABLED | Boolean | true | false |\n| STORAGE_ALLOWED_LOCATIONS | List | gcs://mybucket1/path1/,gcs://mybucket2/path2/ | [] |\n| STORAGE_BLOCKED_LOCATIONS | List | gcs://mybucket1/path1/sensitivedata/,gcs://mybucket2/path2/sensitivedata/ | [] |\n| STORAGE_GCP_SERVICE_ACCOUNT | String | service-account-id@project1-123456.iam.gserviceaccount.com | |\n+-----------------------------+---------------+-----------------------------------------------------------------------------+------------------+\n```\n\n16. Grant `USAGE` on the `FLYWHEEL_APP_GCP` storage integration to the role that the GrowthLoop application will use.\n17. Finally, an external stage will also need to be defined for the storage integration.\n\n```\nCREATE OR REPLACE STAGE flywheel_external_stage\n URL='gcs://outgoing_bucket_name/exports/organization_identifier'\n STORAGE_INTEGRATION = flywheel_app_gcp\n ENCRYPTION = ( TYPE = 'GCS_SSE_KMS');\n```\n\n> 📘\n> \n> Reach out to GrowthLoop to confirm the correct URL string to input in this command!\n\n> 📘\n> \n> The Snowflake user role also needs to have sufficient permissions to load and unload data from this external stage\n> \n> ```\n> grant read, write, usage ON STAGE CUSTOMER_DATA_MODEL.FLYWHEEL_SYSTEM.flywheel_external_stage to role fw_access_role;\n> ```\n\n18. During onboarding, you will see the options pictured below, choose **Snowflake**.\n\n![](https://files.readme.io/52048eb-Untitled_2.png)\n\n19. After selecting Snowflake, you’ll be prompted to enter information for the following fields:\n\n![](https://files.readme.io/78ce013-Screenshot_2024-06-12_at_2.33.46_PM.png)\n\n* **Name:** This will be the name used to refer to your Snowflake DWH in the GrowthLoop Application going forward. This can be any name you choose\n* **Description:** This will be the description associated with your Snowflake DWH in the GrowthLoop Application going forward, should you want to provide one. This is optional and can be any description string you choose.\n* **Account:** This can be pulled from the Snowflake account URL, which is available from the profile menu on the bottom left (see screenshot). The format to input should be `account-identifier.region.cloud-platform` for example: `xy12345.us-central-1.gcp`\n\n![](https://files.readme.io/57c85e0-Screenshot_2024-06-12_at_3.11.21_PM.png)\n\n> 📘\n> \n> The Account string required will change slightly depending on the cloud provider in which your Snowflake account is hosted. Please refer to the Snowflake documentation below for specifics for your cloud provider (AWS, GCP, Azure, etc.). See details [here](https://docs.snowflake.com/en/user-guide/admin-account-identifier.html#non-vps-account-locator-formats-by-cloud-platform-and-regio).\n> \n> ![](https://files.readme.io/d59963b-Untitled_3.png)\n\n* **Username:** This will be the `USER` created in the “Create Snowflake User and Role” Section of this documentation.\n* **Role**: This will be the `ROLE` created in the “Create Snowflake User and Role” Section of this documentation.\n* **Passphrase:** This will be the encryption password used when creating the private key in the “Create Public/Private Key Pair” section of this documentation.\n* **Dataset for snapshots**: The schema name created for storing GrowthLoop audience export snapshots. **Note that this is case sensitive.**\n\n20. After your connection has been established, click **continue** and you will see the following page:\n\n![](https://files.readme.io/1ddd79e-Untitled_4.png)\n\n21. In this section, choose the specific **dataset** and **table** in your data warehouse that you will be activating in GrowthLoop.\n22. Next, select your **unique key** and the fields you wish to show in the criteria builder by default.\n23. Finally, click **Finish** to complete the setup.\n\n![](https://files.readme.io/bbd8096-Untitled_5.png)\n\n> 👍\n> \n> You've connected your Snowflake account to GrowthLoop!\n\n> 📘\n> \n> Having trouble connecting to **Snowflake**? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com), and we’ll be in touch shortly to help resolve the issue!\n\nUpdated 3 months ago\n\n* * *\n\n* [Setup Datasets](https://docs.growthloop.com/docs/setup-datasets)\n* [Setup Dataset Groups](https://docs.growthloop.com/docs/setup-dataset-group)","2024-03-20T21:02:21.523Z","2de11644-ca6a-4aca-af6e-8b401bb4d3e9",[],[],{"_40":1185,"_128":1186,"_130":1187,"_132":1188,"_134":-5,"_13":-5,"_120":1189,"_122":136,"_25":1190,"_138":-5,"_139":1191,"_141":1192},"list audience exports","list-audience-exports","https://docs.growthloop.com/reference/get_api-public-exports","Language\n\nCredentials\n\n \\--url https://app.pub.prod.flywheelproducts.com/api/public/exports \\\\\n\n \\--header 'accept: application/json'\n\nClick `Try It!` to start a request and see the response here! Or choose an example:","2024-03-20T21:02:37.280Z","1921e223-643b-4a36-9ea1-631f621bdf1d",[],[],{"_40":1194,"_128":1195,"_130":1196,"_132":1197,"_134":-5,"_13":-5,"_120":1198,"_122":136,"_25":1199,"_138":-5,"_139":1200,"_141":1201},"list audiences","list-audiences","https://docs.growthloop.com/reference/get_api-public-audiences","Language\n\nCredentials\n\n \\--url https://app.pub.prod.flywheelproducts.com/api/public/audiences \\\\\n\n \\--header 'accept: application/json'\n\nClick `Try It!` to start a request and see the response here! Or choose an example:","2024-03-20T21:02:33.410Z","1e9907f3-b9fb-4305-8f2a-1f94e20dc0d0",[],[],{"_40":1203,"_128":1204,"_130":1205,"_132":1206,"_134":-5,"_13":-5,"_120":1207,"_122":136,"_25":1208,"_138":-5,"_139":1209,"_141":1210},"list dataset groups","list-dataset-groups","https://docs.growthloop.com/reference/get_api-public-dataset-groups","Language\n\nCredentials\n\n \\--url https://app.pub.prod.flywheelproducts.com/api/public/dataset\\_groups \\\\\n\n \\--header 'accept: application/json'\n\nClick `Try It!` to start a request and see the response here! Or choose an example:","2025-06-20T22:59:05.925Z","66f0ccdb-20bf-4b64-97dc-21e2fb690ea6",[],[],{"_40":1212,"_128":1213,"_130":1214,"_132":1215,"_134":-5,"_13":-5,"_120":1216,"_122":136,"_25":1217,"_138":-5,"_139":1218,"_141":1219},"list destinations","list-destinations","https://docs.growthloop.com/reference/get_api-public-destinations","Language\n\nCredentials\n\n \\--url https://app.pub.prod.flywheelproducts.com/api/public/destinations \\\\\n\n \\--header 'accept: application/json'\n\nClick `Try It!` to start a request and see the response here! Or choose an example:","2024-03-20T21:02:37.662Z","1b126b6e-6ff9-4bc2-8a78-43e5c4fb0858",[],[],{"_40":1221,"_128":1222,"_130":1223,"_132":1224,"_134":-5,"_13":-5,"_120":1225,"_122":136,"_25":1226,"_138":-5,"_139":1227,"_141":1228},"list journeys","list-journeys","https://docs.growthloop.com/reference/get_api-public-journeys","Language\n\nCredentials\n\n \\--url https://app.pub.prod.flywheelproducts.com/api/public/journeys \\\\\n\n \\--header 'accept: application/json'\n\nClick `Try It!` to start a request and see the response here! Or choose an example:","2025-06-20T22:59:06.313Z","f12973ae-b9e1-4364-a25c-fdd43420767d",[],[],{"_40":1230,"_128":1231,"_130":1232,"_132":1233,"_134":-5,"_13":-5,"_120":1234,"_122":136,"_25":1235,"_138":-5,"_139":1236,"_141":1237},"Manage your organizations and teams | GrowthLoop Docs","manage-your-organizations-and-teams-growthloop-docs","https://docs.growthloop.com/docs/manage-teams","# Manage your organizations and teams\n\nLearn how to manage organizations and teams in GrowthLoop\n\nIn this article, you'll learn how to manage Teams in GrowthLoop. There are a few key concepts to understand in the GrowthLoop before we get started.\n\n* **Organizations**: Organizations are the top level entity in GrowthLoop. Usually companies have one organization.\n * Organizations can have multiple `Source Connections`to different data clouds.\n * Organizations can have multiple teams.\n* **Teams**: Teams are the defining unit for divisions and groups of people that collaborate often together.\n * Teams can have `dataset groups`and `datasets`\n * Teams can have their own `destinations`\n\n* Navigate to `Organizations` in the left menu rail\n* Click `Invitations`\n* Admins can invite users by inserting email addresses.\n * Select `Team` you are inviting teammate to.\n * Select `Role` you want your teammate to have.\n * Insert a Message they will receive in their email invite.\n\n![](https://files.readme.io/d6b429b-Screenshot_2024-01-23_at_9.29.15_PM.png)\n\n* Your teammates will receive an email asking them to join your GrowthLoop organization.\n* To resend invites simply click `Resend`\n\n![](https://files.readme.io/9e02ccf-send_invites.png)\n\n* Navigate to `Organizations` in the left menu rail\n* Click `Teams`\n\n![](https://files.readme.io/a9a8ca9-organization_teams.png)\n\n* To Create a new team, click `Create Team` and insert team name. You can then add users to team.\n \n ![](https://files.readme.io/a1a7dd5-Screenshot_2024-01-23_at_9.33.55_PM.png)\n* To `Add Users` to a `Team` simply click `Add User to [Team Name` in upper right.\n \n\n![](https://files.readme.io/8dd713f-Screenshot_2024-01-23_at_9.31.49_PM.png)\n\n* To remove users from a `Team` click `Remove` next to their email address.\n\n* To switch between Organizations and Teams, you can use your `Team Toggle` in the left menu rail.\n* You can only view the organizations and teams you belong to.\n* By clicking on an Organization/Team in the `Team Toggle` you will be taken to that Team space.\n\n![](https://files.readme.io/d5ad5d9-Screenshot_2024-01-23_at_9.36.59_PM.png)\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:31.328Z","3551d85d-c12b-43cb-9be2-b993faf8251d",[],[],{"_40":1239,"_128":1240,"_130":1241,"_132":1242,"_134":-5,"_13":-5,"_120":1243,"_122":136,"_25":1244,"_138":-5,"_139":1245,"_141":1246},"Manual mode for customer journeys | GrowthLoop Docs","manual-mode-for-customer-journeys-growthloop-docs","https://docs.growthloop.com/docs/manual-mode","# Manual mode for customer journeys\n\nManual mode is a powerful capability to allow you to manually run a full or parts of a journey at any given time. It's in contrast to running a journey one-time, always or on a specific schedule.\n\n![](https://files.readme.io/4ec51cddbcbce1cd9a80773324e2cba48e73aeb2dfda0254a33e92d7632a7b52-image.png)\n\nIt specifically allow you to run:\n\n* A specific node in a journey\n* A journey **up-to** a specific node\n\n**How it works**\n\nWhen you set up a journey, you must make sure you set its Journey Schedule to **Manual**. This makes sure the journey is ready to manually be run after it's Saved & Published.\n\nAfter you have published the journey, your nodes will have 2 new options next them.\n\n* **Run until this node**\n* **Run this node only**\n* **Run from this node**\n\n![](https://files.readme.io/ff6105c6024caad635d347043ee0223cf4fdc87b2aee1fc845176607e6c489ad-image.png)\n\n**Run until this node**\n\nThis will start the journey and execute every node up-to & including the selected node. It will then stop running any consequent nodes. Keep in mind this will only run any journey paths which somehow **can lead** to this node and not otherwise.\n\n**Run this node only**\n\nThis option will only run customers that are at this node.\n\n**Run from this node**\n\nThis option will execute the selected node and every sub-branch of the journey following that node. Keep in mind this will only run any journey paths leading **out of** the selected node.\n\nThese options are available in journey's manual mode and for the following node types:\n\n1. Entry node\n2. Criteria node\n3. Experiment node\n4. Destination node\n\n**Let's walk through an example that combines the 2 options above**\n\n1. Imagine you have this simple journey, where you check your customers to see if any of them has phone number 4444444.\n \n ![](https://files.readme.io/ce683eeec53cbb5ba9cb3f67bf6a2f3c21cfd88210bfeb6552e81e81a7542ca7-image.png)\n2. You decide to run the journey **until** the success destination node on the bottom left, after you've saved and published the journey.\n \n 1. Notice that all the numbers are 0 in both the pending (yellow) and processed (green) boxes.\n\n![](https://files.readme.io/811af7a55a6f5244fc353fd15bee63cdc67ab87cd724e638e8db1ff99934c122-image.png)\n\n2. You will see the journey is processing and after a minute or two you can refresh the page to see the nodes updated.\n\n![](https://files.readme.io/1ad3265a4f6487be01f3de9e6efe23cac7e7fa42fd536ed5e0bc493f10336981-image.png)\n\n3. You can see that our journey has run and\n \n 1. One user has landed on the success destination node and **was also processed**, which means they were exported to the destination.\n 2. No users were sent to the **Failure destination** node (bottom-right). This is because the journey processor only looks at **the leading path** to the node we ran the journey up to (ie, success destination node).\n4. Now we're going to run the journey differently. We will run it up to the **criteria node** only, to see how this changes the customer distribution.\n \n ![](https://files.readme.io/4d66100c49da43b5fb371202be97ea51071c6a92059f07ef69b8d038a6714bb0-image.png)\n 1. Please note that in our journey settings, we have allowed for users to **re-enter** the journey at every run -- this is recommended for when your journey schedule is set to manual mode.\n \n 2. **This also re-runs the entire journey as if it was the first time we were running it**\n \n ![](https://files.readme.io/759c66681e4a5912c77aed7fb7d5d7a62134a494a4718a1f3f8cd1afa9b0b54c-image.png)\n 3. Let's run the journey until the criteria node\n \n ![](https://files.readme.io/ef7512ce4bdd5bfa97b9da2e1d45985445057927be4e8308787ab71605650ccd-image.png)\n5. Now you can see that both destination nodes have users in their pending (yellow) box.\n \n 1. This is because the journey runs and processes the criteria node and pushes the users to their respective nodes and stops.\n \n ![](https://files.readme.io/15bd95945f945e6c902079387cec2d4432a22b6d11df9c0ffe4bfc5be01cf81d-image.png)\n 1. you can now run each node separately to have your respective users be exported to their respective destinations.\n\n**Edit a journey after it's published**\n\nOne of the key values of manual mode, is that you can edit your journey **after** it's published. If you realize you didn't set up your criteria node correctly, you can update it and run the journey up to that node again.\n\nKeep in mind that you can run a journey in manual mode until you feel confident about your setup, before changing the settings to a different schedule.\n\nYou can only switch the schedule **from** manual mode to any other schedule and never to manual mode from another schedule.\n\n![](https://files.readme.io/70b109b7d89e8ab2a0bc8a3c0adc65f3cdebbe29f1ed22103d39a4b5eaf51f6d-image.png)\n\nOnce you change the settings and save the journey, you'll have to confirm the following changes before they take effect.\n\n![](https://files.readme.io/3298e6c70e96797ff43d16633068748a712e48bc3e30b6047d3d2a3b5fe433b5-image.png)\n\n**Some use cases**\n\n1. Imagine you have a criteria node and want to see how many of your users meet or don't meet the criteria, when they reach that node. Use the \"Run until this node\" option on the criteria node at hand.\n2. Imagine you have an experiment node and want to know how your customers get distributed after the run through that node. Use the \"Run until this node\" option on the experiment node.\n3. Imagine you want to slowly walk through each node in the journey. Use the \"Run this node only\" as you traverse through the journey, to see the impact of each node.\n4. Rerun the same journey -- This is helpful to modify your journey and re-run a flow up to a certain node until you reach your desired behavior\n\n**Change your entry audience**\n\nIf you ever need to, you can change the entry audience to the journey ( **in manual mode** and before hitting publish). However, given a journey can rely heavily on your datasets' fields, changing an entry audience could cause a lot of errors. For example\n\n* Your criteria could be relying on a field that doesn't exist anymore\n* Your match or additional fields on destination nodes might be invalid\n* Your custom attribute formulas could be referencing fields that don't exist in the new entry audience\n* and more\n\nBut with GrowthLoop, you'll be able to see where these errors may be through our new Error Panel mode:\n\n![](https://files.readme.io/906a76444f5ba2b40b0aca08708ac00b085348da826d4de8bd4e2aa77802bfc2-image.png)\n\nThis right-hand panel allows you to refresh the errors (top-right) and by clicking on each error, you can see which dependant fields are causing issues for you to fix.\n\nWe hope this allows you to change your entry audience when needed, without having to create copies of your journey.\n\nUpdated 5 months ago\n\n* * *","2025-06-20T22:58:20.552Z","3e775a54-b689-492c-8d39-decf832f2b93",[],[],{"_40":1248,"_128":1249,"_130":1250,"_132":1251,"_134":-5,"_13":-5,"_120":1252,"_122":136,"_25":1253,"_138":-5,"_139":1254,"_141":1255},"Marketing Cloud Data Extensions","marketing-cloud-data-extensions","https://docs.growthloop.com/docs/salesforce-marketing-cloud-sync","Enhance your Salesforce Marketing Cloud (SFMC) campaigns with powerful customer data from your data warehouse.\n\nIn this guide, we’ll walk you through syncing customer data from your data warehouse into Salesforce Marketing Cloud (SFMC) to supercharge your marketing efforts. Let's get started!\n\nGrowthLoop enables syncing to the `Data Extension` object.\n\n| Object | Description | Sync Modes | Field Mappings (Required) | Field Mappings (Optional) |\n| --- | --- | --- | --- | --- |\n| `Data Extension` | A table that stores customer details for campaigns—keep it accurate with regular syncs for effective personalization | Insert Only (adds new records)

Update Only (modifies existing record attributes)

Upsert (combines insert and update) | `Subscriber Key`: Unique identifier for each subscriber

AND

`Email`: The email associated with each subscriber | * \\*Custom Fields\\*\\*: Include any attribute you've defined in your Data Extension |\n\n* Make sure you've set up **SFMC user permissions**, created an **API integration**, and configured **data extension permissions**. If you haven’t done these yet, you can follow our guide [here](https://docs.growthloop.com/docs/salesforce-marketing-cloud#requirements) to get everything sorted.\n \n* Have your **Subdomain**, **Client ID**, and **Client Secret** ready. You can find these details in SFMC where you set up the API integration.\n \n ![](https://files.readme.io/9f8357a-sfmc_required_credentials.png)\n\n1. Log in to **GrowthLoop** and click **Destinations** on the left sidebar.\n2. Click **New Destination** in the top right corner.\n3. Search for \"Marketing Cloud\" and click **Add Marketing Cloud**.\n4. Enter the required information in the modal, then click **Create**.\n 1. **Destination Name**: This is how the destination will be named and referred to in the app going forward.\n 2. **Sync Frequency**: This indicates how frequently audiences will be synced to the destination.\n 3. **Subdomain**: This is part of the **Authentication Base URI** used for authentication requests. It's the section between **https://** and **.auth.marketingcloudapis.com/**.\n 4. **Client ID**: This is your identifier to access the API. You can find it in SFMC where you set up the API integration.\n 5. **Client Secret**: This is your secret string to securely authenticate your requests. You can find it in SFMC where you set up the API integration.\n\n5. Navigate to the **Syncs** tab on the left sidebar and click **Create Sync** in the top right corner.\n6. Set up your Sync with the following details:\n 1. **Sync Name:** A clear, friendly name for your sync.\n 2. **Sync Frequency:** How often data should sync to the destination.\n 3. **Update Rule:** The default method for syncing data to the destination. GrowthLoop supports `Insert Only` (adds new records), `Update Only` (modifies existing record attributes), and `Upsert` (combines insert and update)\n 4. **Dataset / Table:** The table containing your user data.\n 5. **Dataset Unique Field:** The column with unique values for each user in the table.\n 6. **Match Field:** The column used to identify users in your source table for the destination system. Please select a field that is a unique identifier for each record in the table (e.g, `User ID`, `Email`, etc.)\n 7. **Connection:** Choose the destination for syncing data. Select **Marketing Cloud**.\n 8. **Object Type:** Choose the specific Data Extension to sync in the drop-down.\n 9. **Match Field:** The column used to match and identify users in the destination system based on your source data. Please select `SubscriberKey`\n7. After selecting/inserting the required fields, click **Save Sync**.\n8. Next, add your desired field mappings. SFMC requires both **Email** and **Subscriber Key** to be mapped.\n9. Under **Source**, open the drop-down and select the field containing email addresses.\n10. In the **Destination** section, choose **Email Address** from the drop-down menu, unless already selected.\n11. Click **Add Mapping** to add another **Source > Destination** row.\n12. In the **Source** section, select the field containing a unique identifier for each record (e.g., `User ID`).\n13. Then under **Destination**, choose **SubscriberKey** from the drop-down menu, unless already selected.\n14. Map any other fields you want to insert or update in the Data Extension.\n15. After mapping all the fields, clicking **Update Sync** will prompt you with the following two options:\n 1. **Updates Only:** We recommend you go with the this option, especially if you’re setting up the sync for the first time.\n 2. **Back-fill**: This option is when you are updating an existing Sync with newly mapped fields and you’d like all your **already synced events** to have those fields backfilled for them. This operation can be very expensive and time consuming on your underlying Data Warehouse, so please choose that option if you’re absolutely sure.\n16. Once complete, return to your sync and enable it by clicking the **toggle** at the top of the page\n17. To confirm that your sync has been successfully sent to SFMC, navigate to the **Subscribers** section and select the Data Extension to view the updated records and attributes.\n\n![](https://files.readme.io/c3df40b-image.png)\n\n> 👍\n> \n> You have successfully created a sync to a `Data Extension` in SFMC!\n\n> 📘\n> \n> If you experience any issues when connecting to or creating syncs to SFMC Data Extensions, please reach out to us at [support@growthloop.com](mailto:support@growthloop.com), and we’ll be in touch shortly to help resolve the matter!\n\nUpdated 5 months ago\n\n* * *","2025-06-20T22:58:05.421Z","e6c6f752-4414-43fa-beb7-a7777ff2f48a",[],[],{"_40":1257,"_128":1258,"_130":1259,"_132":1260,"_134":-5,"_13":-5,"_120":1261,"_122":136,"_25":1262,"_138":-5,"_139":1263,"_141":1264},"Marve: Use generative AI to build audiences | GrowthLoop Docs","marve-use-generative-ai-to-build-audiences-growthloop-docs","https://docs.growthloop.com/docs/marve","# Marve: Use generative AI to build audiences\n\n## Marve Studio\n\nBuild audiences leveraging the power of Generative AI\n\nIn this article, we will walk you through the steps to get Marve enabled within the GrowthLoop web application. Once enabled, you will be able to utilize a new form of audience building using generative AI!\n\nMarketers write their briefs in natural language and describe their audiences with words. To meet marketers where they’re at, GrowthLoop developed Marve.\n\nMarve, short for Marketing Velocity, is an innovative offering that leverages the power of generative AI to turn a written prompt that describes a target audience into a tangible audience segment.\n\nMarve utilizes large language models (LLMs) through OpenAI and Gemini support. Columns within your data tables that are connected to GrowthLoop from your data warehouse are analyzed through LLMs. JSON query is generated and converted to an audience graph. The marketing end user is displayed the results within the GrowthLoop UI.\n\nNo coding is required. Simply write out who you wish to target and if the data exists within your connected data sets, voila, an audience will be generated! An example is provide below.\n\nMarve is available in Limited Beta today. Current customers may contact their Solutions Architect to learn more and prospects can fill out the form at the bottom of this page to join the waitlist.\n\nSign into GrowthLoop and navigate to Datasets from the left menu:\n\n![](https://files.readme.io/6fe503d-datasets_navigation.png)\n\nYou need to select a specific Dataset Group —> Marve (tab) and check the box to Opt-in for Marve\n\n![](https://files.readme.io/4051511-marve_consent.png)\n\nGreat! You are now enabled to use Marve. Navigate to “Audiences” from the left menu and select “New Audience” from the upper right corner. Select \"Build with Marve\"\n\n![](https://files.readme.io/127ac6e-build_with_marve.png)\n\nInsert your business goal into Marve and click “Generate Audience” to begin brainstorming new audience targets to help you achieve your marketing goals.\n\nThe audience will be generated automatically for review. View the live size of the audience, make edits, and add additional filters to refine your target segment, just like you would with the standard Audience Builder functionality.\n\n![](https://files.readme.io/f163d8e-marve_extend_audience.png)\n\n[Learn more about Marve.](https://www.growthloop.com/post/introducing-marve)\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:31.426Z","684d24ca-f402-4d36-84d1-35cac1f2800d",[],[],{"_40":1266,"_128":1267,"_130":1268,"_132":1269,"_134":-5,"_13":-5,"_120":1270,"_122":136,"_25":1271,"_138":-5,"_139":1272,"_141":1273},"Microsoft Ads (Bing) Conversions","microsoft-ads-bing-conversions","https://docs.growthloop.com/docs/microsoft-ads-bing-offline-conversions","Learn how to create Syncs for Microsoft Ads (Bing) Offline Conversions\n\nIn this guide, we'll walk you through syncing offline conversion data from your data warehouse to your Microsoft Ads campaigns using GrowthLoop. Let's get started!\n\nGrowthLoop enables syncing to the following Microsoft Ads (Bing) object:\n\n| Object | Description | Sync Modes | Field Mappings (Required) | Field Mappings (Optional) |\n| --- | --- | --- | --- | --- |\n| `Conversion` | Sync and track offline behavior | Insert (adds new events) | `Conversion Name`: The name of the existing conversion goal in your Bing Ads account

`Conversion Time`: The exact date and time of the conversion in UTC format. It must be within 90 days of the click.

`Microsoft Click ID`: The unique identifier assigned to a click. | See full list of parameters [here](https://learn.microsoft.com/en-us/advertising/campaign-management-service/offlineconversion?view=bingads-13) |\n\n* Have a Microsoft Ads (Bing) account. Create one [here](https://help.ads.microsoft.com/#apex/ads/en/53090/0)!\n* Connect Microsoft Ads (Bing) as a destination to your GrowthLoop account. Click [here](https://docs.growthloop.com/docs/microsoft-ads) for detailed instructions.\n\n1. Click **Syncs** on the left sidebar.\n \n2. Then click **Create Sync** on the upper right hand-side.\n \n3. Next, configure your sync by filling out the following fields:\n \n 1. Route Name:\n \n 1. **Name:** A friendly name for the sync.\n 2. **Sync Frequency**: The default frequency for syncing data to Microsoft Ads (Bing). The options are: **15 minutes**, **30 minutes**, **hourly**, and **daily**.\n 3. **Update Rule:** The default operation for syncing data to Microsoft Ads (Bing).\n 2. Source:\n \n 1. **Dataset/Table:** The table that holds the data you want to sync to Microsoft Ads (Bing). Usually, it's organized within an events table.\n 2. **Dataset Unique Field(s):** The unique field(s) on the table. They will populate automatically after selecting the Dataset/Table.\n 3. **Match Field**: The column used to match and identify conversions from your source table in Microsoft Ads (Bing). Please select the field that contains the name of the conversion.\n 3. Destination:\n \n 1. **Connection:** The destination you will sync data to. Please select **Microsoft Ads (Bing)**.\n 2. **Object Type:** The object that you want to send data to. Please select **Conversion**.\n 3. **Match Field:** The column used to match and identify conversions from Microsoft Ads (Bing) in your source table. Please select **Conversion Name**.\n4. Once you finish selecting/inserting the required fields, click **Save Route**.\n \n5. Next, set up the field mappings to start your sync. Microsoft Ads (Bing) needs at least three of the following fields mapped: **Conversion Name**, **Conversion Time**, and **Microsoft Click ID**. Let's begin with **Conversion Time**. Choose the field from your table that contains the date and time of the offline conversion.\n \n **Important**: The date and time must be within the last 90 days and value must be in Coordinated Universal Time (e.g. 2020-04-30T17:02:35.6853793Z)\n \n6. Then, under the Destination section, choose **Conversion Time** from the drop-down menu, unless it has been automatically selected for you.\n \n7. Next up, let’s map **Conversion Name**. Pick the field from your table that holds the conversion goal name. Ensure you create the Conversion Name beforehand in Microsoft Ads.\n \n\n> 📘\n> \n> Uploading conversions requires a 2-hour wait after creating the goal. Failure to wait may result in offline conversion data not being applied.\n\n8. Then, under the Destination section, choose **Conversion Name** from the drop-down menu, unless it has been automatically selected for you.\n9. Lastly, choose the field in your source table that contains **Microsoft Click IDs** associated with the conversion, and map it to the destination.\n\n> 📘\n> \n> Microsoft Click IDs (MSCLKIDs) are unique identifiers assigned to each click on your Microsoft Advertising ads. MSCLKIDs are automatically appended to your landing page URL when someone clicks on your ad, provided that auto-tagging is enabled. If you haven't enabled it yet, [click here](https://help.ads.microsoft.com/apex/index/3/en/60000) to learn how.\n\n10. After clicking **Update Route**, return to your sync and enable it by clicking the toggle at the top of the page!\n\n> 👍\n> \n> You've successfully created a conversion sync to Microsoft Ads (Bing)! You should now be able to see it in your Syncs table.\n\nTo confirm that your offline conversion data has been received, go to the **Conversion Tracking > Offline Conversions** section and check for the newly uploaded conversions under your Conversion Goal. It may take up to 5 hours for conversions to appear. Failures can occur if the conversion dates are not within the last 90 days and not formatted in Coordinated Universal Time (e.g., 2020-04-30T17:02:35.6853793Z).\n\n![](https://files.readme.io/141b509-Untitled_8.png)\n\n> 📘\n> \n> If you experience any issues when connecting to Microsoft Ads (Bing) Offline Conversion Sync, please reach out to us at [support@growthloop.com](mailto:support@growthloop.com), and we’ll be in touch shortly to help resolve the matter!\n\nUpdated 5 months ago\n\n* * *","2024-04-24T23:07:51.128Z","347d9002-769f-4041-a8f0-bfd7c3d412ea",[],[],{"_40":1275,"_128":1276,"_130":1277,"_132":1278,"_134":-5,"_13":-5,"_120":1279,"_122":136,"_25":1280,"_138":-5,"_139":1281,"_141":1282},"Microsoft Azure Blob Storage | GrowthLoop Docs","microsoft-azure-blob-storage-growthloop-docs","https://docs.growthloop.com/docs/microsoft-azure-blob-storage","Export audiences from your data warehouse to Azure Blob Storage via SFTP for storage and activation.\n\nIn this article, we will walk you through the steps to get **Azure Blob Storage** connected as a destination in the GrowthLoop web application. Once connected, you will be able to send your audience segments to Azure Blob Storage via SFTP for storage and activation!\n\n* Have an Azure account. Click [here](https://azure.microsoft.com/en-us/free/) to sign up for a free trial if you do not.\n* Create a storage account. Click [here](https://learn.microsoft.com/en-us/azure/storage/common/storage-account-create?toc=%2Fazure%2Fstorage%2Fblobs%2Ftoc.json&bc=%2Fazure%2Fstorage%2Fblobs%2Fbreadcrumb%2Ftoc.json&tabs=azure-portal) to learn how.\n* Enable SFTP support for an existing storage account. Click [here](https://learn.microsoft.com/en-us/azure/storage/blobs/secure-file-transfer-protocol-support-how-to?tabs=azure-portal) to learn how.\n* Create a local user with the necessary permissions to write data to the storage account. Click [here](https://learn.microsoft.com/en-us/azure/storage/blobs/secure-file-transfer-protocol-support-how-to?tabs=azure-portal) to learn how.\n\n1. When you sign into the GrowthLoop platform, navigate to the **Destinations** tab on the left sidebar and click **New Destination** in the top right corner.\n \n2. When the **Select Destination** window pops up, type **Azure** into the search bar and click **Add Azure Blob Storage**.\n \n ![](https://files.readme.io/4f3bd0a-Untitled_1.png)\n3. Clicking **Add Azure Blob Storage** will require you to select/insert the following information:\n \n 1. Destination Info:\n \n 1. **Destination name:** This is how the destination will be named and referred to in to the app going forward. It is helpful to make this name “marketer friendly” so everyone on your team knows its purpose.\n 2. **Sync frequency**: This is the default frequency audiences will be synced to a destination. Marketers can always change frequency of an export to Azure Blob Storage, but this sets the default.\n 2. Credentials:\n \n 1. **Account**: Azure Blob Storage account name\n \n 2. **Username**: The username specified during the local user setup\n \n 3. **Password**: The password specified during the local user setup\n \n ![](https://files.readme.io/244d3f1-Untitled_2.png)\n4. Go ahead and select **Create**, and we’ll validate we have all the proper permissions to load audience data. You should now see **Azure Blob Storage** in your list of connected destinations!\n \n ![](https://files.readme.io/3d8b886-Untitled_3.png)\n\n1. Log in to the [Azure Portal](https://portal.azure.com/).\n2. Go to Storage Accounts.\n3. Choose the account you set up to store audience files during Step 3 in the Set Up Destination section.\n4. Click on Containers in the sidebar.\n\n![](https://files.readme.io/630c68e-Untitled_8.png)\n\nExperiencing any issues when connecting to **Azure Blob Storage**? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and we’ll be in-touch shortly to help resolve the matter!\n\nUpdated 5 months ago\n\n* * *","2024-04-10T18:41:42.208Z","0a34560b-7790-4464-ba4e-ee70bd7d48af",[],[],{"_40":1284,"_128":1285,"_130":1286,"_132":1287,"_134":-5,"_13":-5,"_120":1288,"_122":136,"_25":1289,"_138":-5,"_139":1290,"_141":1291},"Our security commitment at GrowthLoop | GrowthLoop Docs","our-security-commitment-at-growthloop-growthloop-docs","https://docs.growthloop.com/docs/overview-security","# Our security commitment at GrowthLoop\n\n## Overview\n\nLearn about GrowthLoop's Security posture\n\nThe GrowthLoop platform was designed to query your data in place, so your data never leaves your data cloud. Meaning, we avoid storing any of your data in our platform.\n\n![](https://files.readme.io/5e96d15-growthloop_architecture.png)\n\n* **Query in Place**: GrowthLoop queries your data cloud directly, and you can provide a cloud bucket to store any exports so no data is stored on GrowthLoop infrastructure.\n* **Bring your own Export Storage**: The GrowthLoop platform stores some data in storage buckets to route data to the marketing platform or power other features like debug logs. Your team has control over whether you choose to use a GrowthLoop-managed storage bucket or bring your bucket (BYOB).\n* **SOC 2 Compliant**: GrowthLoop is SOC2 Type 2 certified and we will continue to maintain and be audited by third-party auditors regularly.\n\n> 📘\n> \n> Contact [support@growthloop.com](mailto:support@growthloop.com) to do an architecture review.\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:32.592Z","5c49d4c9-dc26-449c-b5e8-be29c718d279",[],[],{"_40":1293,"_128":1294,"_130":1295,"_132":1296,"_134":-5,"_13":-5,"_120":1297,"_122":136,"_25":1298,"_138":-5,"_139":1299,"_141":1300},"Pinterest","pinterest","https://docs.growthloop.com/docs/pinterest","Learn how to send conversion data to Pinterest for a more comprehensive view of your campaign performance. Let's get started!\nTo begin, sign into the GrowthLoop Platform and navigate to the Destinations tab on the left sidebar. Click New Destination in the top right corner.\nIn the Select Destination window that appears, just type Pinterest into the search bar. Then, click Add Pinterest.\nIn the window, please enter the following information to set up the connection to the destination.\nDestination Name: This is how the destination will be named and referred to in the app going forward.\nSync Frequency: Choose between Hourly or Daily to determine how frequently GrowthLoop exports audiences to Pinterest.\nSelect Ad Account: Choose the account where you would like to receive GrowthLoop audiences.\nAccess & Refresh tokens: These can be found in your Pinterest Ads manager under Ads > Conversions\nOnce you've entered the information, click on Create. We'll check to make sure we have all the necessary permissions to send audience data to Pinterest. If everything is in order, you'll now find the new Pinterest Destination in your list of connected destinations.\nTo route the latest conversion events (e.g., web, in-app, offline) to Pinterest, go to the Signals/Syncs tab on the left sidebar and click New Signal Route in the top right corner.\nClicking Create Signal Route will require you to select/insert the following information:\nRoute Name: A friendly name for the signal route.\nSync frequency: The default frequency for syncing the latest conversion info to a destination.\nUpdate Rule: The default operation for syncing the latest user info to a destination. Update only changes existing data, Insert only inserts new data, and Insert or update is a hybrid action that adds new data if it's not already present or updates it if it is.\nSource Dataset/Table: The table that holds the latest user info. Usually, it's organized within an Events table.\nSource Dataset Unique Field: The column that contains values that are distinct for each user in the table.\nSource Match Field: The column used to match and identify users from your source table in the destination system. Please select the column that contains either MAID, Hashed Email, Client IP Address.\nDestination Connection: The destination you will sync data to. Please select the Pinterest destination you set up in the previous step.\nDestination Object Type: The object you want to send data to. Please select Conversion Event.\nDestination Match Field: The column used to match and identify users from the destination system in your source table. Depending on what you selected as your Source Match Field, choose MAID, Hashed Email, or Client IP Address.\nOnce you finish selecting/inserting the required fields, click Save Route.\nIt's time to add the field mappings to activate your signal route. The following fields are required: Action Source, Event Name, Event ID, and Event Time (timestamp). In addition, you must select either Emails or Hashed MAID (List) or both Client IP Address and Client User Agent.\nTo map the fields, navigating to the Field Mapping section. Choose the columns that correspond to the required Destination Fields from the drop-down menu under Source.\nTo include extra mappings for the other fields, click on Add Mapping. This will generate a new row for Source > Destination.\nLook for and choose the fields in your source table for the remaining items.\nFinally, click the toggle at the top of the page to enable the sync!\nCongratulations - you have successfully created a conversion sync to Pinterest!\nUpdated 3 months ago","2024-03-20T21:02:36.095Z","ffdc08a2-8e56-4ffd-a7cf-3e17d6a936a0",[],[],{"_40":1302,"_128":1303,"_130":1304,"_132":1305,"_134":-5,"_13":-5,"_120":1306,"_122":136,"_25":1307,"_138":-5,"_139":1308,"_141":1309},"Preparing Customer Data","preparing-customer-data","https://docs.growthloop.com/docs/preparing-customer-data","Learn how to prepare your customer data for GrowthLoop\n\nWith GrowthLoop, you can start building audiences and exporting them to your favorite destinations within minutes. One of the key first steps is to prepare your customer data for easy integration with our web application.\n\nGrowthLoop accepts any type of table in your data cloud for activation. In this article, we'll be going over three key types of data we see customers use: Customer Details, Transactions, and Events.\n\n![](https://files.readme.io/0740112-full_schema.png)\n\nTo get started you only need to hook up one dataset to GrowthLoop - your Customer Details dataset. Simply identify this table in your data warehouse, label a few fields, and away you go.\n\nThere are a few things GrowthLoop will ask for in this table when you are setting up:\n\n* **Customer Unique ID:** You must have a unique ID on your table that identifies a customer. This is how GrowthLoop splits your audiences into treatment and control groups. You can use identifiers that are 100% populated like email or mobile device ID, but we do not encourage it as uniqueness is not always guaranteed across all your customers.\n* **Email:** Email address of user. This field is used to match to Destinations.\n* **Device ID:** Mobile Device ID of user. This field is used to match to Destinations.\n* **Total Spend (optional):** Total spend of user with your company. This field is used in the Audience Report to show your team how much revenue they are targeting with their audience.\n* **Additional Attributes Fields (optional):** We encourage you to add as many attributes to your Customer Details Dataset as possible to filter on and empower your business teams when creating an audience.\n\n‍\n\n![](https://files.readme.io/cead59d-customer_schema.png)\n\nConnect a Transactions Dataset to create dynamic audiences based on when customers purchase, their purchases, and how much they spend. This table should contain all your customers' purchases, or at least as many as you have readily available.\n\nHere are a few examples of powerful fields to include in your Transactions table:\n\n* **Customer Unique ID (mandatory):** This is your Customer Unique ID to identify the user that made the transaction and to connect to the Customer Details table discussed above.\n* **Category:** Category of item purchased\n* **Price:** Price of item purchased\n* **Discount Code:** A field identifying if a coupon code was used and what type.\n* **Return or Exchange**: A field identifying whether this was a return or exchange.\n* **Purchase Timestamp:** Timestamp when item was purchased\n* **Additional Attribute Fields:** We encourage adding as many attributes to your Transactions Dataset as you like, so your business teams can create audiences based on when your customers buy.\n\nDo you have multiple types of Transactions in different tables? Don’t sweat it. You can add multiple Transaction Datasets to GrowthLoop to create audiences on each. Just make sure each has the Customer Unique ID tied in.‍\n\nAdd an Events Dataset to create dynamic audiences based on other user event data such as web app/mobile app usage, email opens, ticket scans, survey logs, and/or customer service logs. You are able to add multiple Events Datasets, just like Transactions, so long as each has the Customer Unique ID available for matching.\n\nExamples of Events fields are:\n\n* **Customer Unique ID (mandatory):** This is your Customer Unique ID to identify the user that performed the event and to connect to the Customer Details table discussed above.\n* **Event Name:** Name of event\n* **Event Timestamp:** Timestamp when item was purchased\n* **Type:** Category of event performed\n* **Value:** Value of Event\n* **Additional Attribute Fields:** We encourage you to add as many attributes to your Events Dataset as you like so your business teams can create audiences based on when your customers perform actions. \n ‍\n\nIf you are unsure if your customer data model fits neatly into one of these three dataset types or your Data Warehouse does not currently have a single view of your customer, please contact us at [support@growthloop.com](mailto:support@growthloop.com) We would love to brainstorm solutions together with you to enable your teams to get up and running within the GrowthLoop app as soon as possible!\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:23.218Z","6ec50883-eaf6-418f-9ebf-18d6d1b46d63",[],[],{"_40":1311,"_128":1312,"_130":1313,"_132":1314,"_134":-5,"_13":-5,"_120":1315,"_122":136,"_25":1316,"_138":-5,"_139":1317,"_141":1318},"PulsePoint","pulsepoint","https://docs.growthloop.com/docs/pulsepoint","Learn how to connect and send audiences to PulsePoint\n\nIn this article, we'll guide you through connecting PulsePoint to GrowthLoop and exporting your audiences to the destination.\n\nPulsePoint, a leading programmatic platform, specializes in health data and real-time ad targeting, making it a powerful tool for reaching highly specific audiences in the healthcare sector.\n\n* Make sure you have a **PulsePoint account**. If you don't, fill out this [form](https://www.pulsepoint.com/contact) to get in touch with a rep!\n* Make sure you have your **API credentials** handy, including `Client ID`, `Client Secret`, and `Account ID`. If you don't have them, please contact your rep!\n\n> 📘\n> \n> **Note**\n> \n> PulsePoint lists cannot exceed **1 million unique NPIs**. GrowthLoop automatically dedupes before each export, but exports larger than this must be split into separate audiences or reduced to avoid export errors.\n\n1. Log into **GrowthLoop** and click the **Destinations** tab on the left sidebar.\n \n2. Then click **New Destinations** on the upper right side.\n \n3. Next, search for **PulsePoint** in the destination modal and click **Add PulsePoint**.\n \n4. Enter the required information in the modal, then click **Create**.\n \n 1. `Destination`: Enter the name you want to give the destination.\n 2. `Sync Frequency`: Select a default export frequency to the destination.\n 3. `Advertiser`: Enter the name of the advertiser you're uploading NPI lists to.\n 4. `Username`: Enter your sign-in email.\n 5. `Password`: Enter your sign-in password.\n 6. `Account ID`: Enter the Account ID provided by your rep.\n 7. `Client ID`: Enter the Client ID provided by your rep.\n 8. `Client Secret`: Enter the Client Secret provided by your rep.\n\n5. Navigate to your list of audiences by clicking the **Audiences** tab on the left sidebar.\n6. Choose an existing audience or create a new one. Need help creating? Click [here](https://docs.growthloop.com/docs/create-an-audience) to learn how!\n7. Once created, click the **Export** button on the upper right side.\n8. Search for **PulsePoint** in the export modal and then click **Add PulsePoint**.\n9. Please map the column containing NPIs to the `NPIs (Required)` field under **Configure Match Field Settings**, then click **Next**.\n10. Configure your export settings:\n 1. **Export Name**: Automatically populated with your audience name for easy identification in the destination.\n 2. **Campaign Type**: Choose between a one-time export or ongoing basis.\n 3. **List Status**: Choose between **New** or **Existing**.\n 1. `New`: Selected by default, this option will create a new NPI list, using the audience name as the list name, and export NPI records to it.\n 2. `Existing`: This option will export NPI records to the specific NPI list you select using its **List ID**. To find the List ID, navigate to the **Campaign NPI Lists** section in PulsePoint and click on the desired list. The List ID is the last part of the URL (e.g., [https://platform.pulsepoint.com/Buyer/#/setup/npilist/**123456**](https://platform.pulsepoint.com/Buyer/#/setup/npilist/**123456**)).\n 4. **Advertiser (Required)**: The advertiser name will automatically populate based on your input when creating the destination. You can change it if you wish!\n 5. **PulsePoint Product (Required)**: Specify the product within PulsePoint to which you would like to upload NPI lists. Currently, we only support `LIFE`.\n 6. **Export Schedule**: Set the frequency, start date, end date, and specific days of the week.\n 7. **Additional Fields**: Add additional fields you would like to append to your NPI list. Please note:\n 1. You can't add more than 35 additional fields to your NPI list.\n 2. If you set the \"Campaign Type\" to \"Ongoing\" and include additional fields (i.e. attributes), newly added audience members since the last export will override the previous list. For example, if your first export contains 10 NPIs and the next export includes only 2, the entire NPI list will now only contain the 2.\n11. Finally, click **Export** to send the audience to PulsePoint!\n\n> 👍\n> \n> You have successfully exported the audience!\n\nTo view your list, log in to your PulsePoint account, click the hamburger menu on the left-hand side, and select **Campaign NPI Lists** under **Lists**.\n\n![](https://files.readme.io/204a6d7b60fb2056d93cfec4d2dc0f1cba979a08330da43209cc6c918785a9c7-image.png)\n\n> 📘\n> \n> Experiencing any issues when connecting and/or exporting to **PulsePoint**? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and we’ll be in touch shortly to help resolve the matter!\n\nUpdated about 1 month ago\n\n* * *","2025-06-20T22:58:58.825Z","1e6002e0-08b9-45b0-b935-e52942651ca1",[],[],{"_40":1320,"_128":1321,"_130":1322,"_132":1323,"_134":-5,"_13":-5,"_120":1324,"_122":136,"_25":1325,"_138":-5,"_139":1326,"_141":1327},"Qualtrics","qualtrics","https://docs.growthloop.com/docs/qualtrics","Learn how to connect and send audiences to Qualtrics\n\nIn this article, we'll guide you through connecting Qualtrics to GrowthLoop and exporting your audiences to the destination.\n\nQualtrics is an experience management platform that helps organizations collect, analyze, and act on customer, employee, product, and brand feedback through advanced surveys and analytics.\n\n> 📘\n> \n> Your Qualtrics account must be whitelisted for `Early Access Program` access. If it isn’t, please reach out to your Qualtrics rep to request access.\n\n* Make sure you have a **Qualtrics** account. If you don't, fill out this [form](https://www.qualtrics.com/contact/?utm_lp=support+homepage) to connect with their sales team!\n* Have your `Data Center ID`, `Directory ID*`, and `API Token` ready - you’ll need them to connect to your account. To find them, click on your **profile icon** in the top right, select **Account Settings**, and look under the **User** and **API** sections.\n* Confirm that your `API Token` has the following scopes:\n * `read:mailing_list_contacts`: Access contacts in your mailing lists.\n * `write:mailing_list_contacts`: Change or delete contacts in your mailing lists, or create new contacts in your mailing lists.\n * `write:contact_transactions`: Access your contacts’ transactions in your directories.\n\n1. Log into **GrowthLoop** and click the **Destinations** tab on the left sidebar.\n \n2. Then click **New Destinations** on the upper right side.\n \n3. Next, search for **Qualtrics** in the destination modal and click **Add Qualtrics**.\n \n4. Enter the required information in the modal, then click **Create**.\n \n 1. `Destination Name`: Enter the name you want to give the destination.\n 2. `Sync Frequency`: Select a default export frequency to the destination.\n 3. `Data Center ID`: Input your Data Center ID, which can be found in **Account Settings** under the **User** section.\n 4. `Directory ID`: Input your Directory ID, which can be found in **Account Settings** under the **User** section.\n 5. `API Token`: Input your API Token, which can be found in **Account Settings** under the **API** section.\n\n5. Navigate to your list of audiences by clicking the **Audiences** tab on the left sidebar.\n6. Choose an existing audience or create a new one. Need help creating? Click [here](https://docs.growthloop.com/docs/create-an-audience) to learn how!\n7. Once created, click the **Export** button on the upper right side.\n8. Search for **Qualtrics** in the export modal and then click **Add Qualtrics**.\n9. Then, map the field in your table that contains the user’s email address to the `Email` user identifier field in **Configure Match Field Settings**. This step is required to proceed. Once mapped, you can also optionally include `First Name`, `Last Name`, `External Reference ID`, `Unsubscribed`, `Phone`, and `Language` fields.\n10. Configure your export settings:\n 1. `Export Name`: Automatically populated with your audience name for easy identification in the destination.\n 2. `Campaign Type`: Choose between **One Time** to export the audience once or **Ongoing** to continuously export new audience members as they qualify.\n 3. `Export Inclusion Criteria`: Choose between **All audience members** to export the full audience or **Newly added audience members** to export only those who have been added since the last export.\n 4. `Add Contacts to`: Choose to add contacts to a **Mailing List** for sending targeted surveys. In the future, support for adding contacts to **XM Directory** will be available.\n 5. `Mailing List Status`: Choose between **New** to create a new contact list using the audience name, or **Existing** to add users to an existing segment by providing a **Mailing List ID**.\n 6. `Export Schedule`: Configure the **Frequency**, **Start Date**, **End Date**, and specific **Days of the Week** (only for **Ongoing** exports).\n 7. `Additional Fields`: Add extra fields to your export for personalization, with the option to alias the output for further customization.\n11. Finally, click **Export** to send the audience to **Qualtrics**!\n\n> 👍\n> \n> You have successfully exported the audience!\n\nTo view your audience, log in to **Qualtrics**, click **Directories** in the left-hand sidebar, navigate to the **Segments & Lists** tab, and find your audience name in the table!\n\n![](https://files.readme.io/888d0f1eef2ce9dea397802661741b31efbf5449c4d83d579c83510ff4855529-image.png)\n\n> 📘\n> \n> Experiencing any issues when connecting and/or exporting to **Qualtrics**? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and we’ll be in touch shortly to help resolve the matter!\n\nUpdated 3 months ago\n\n* * *","2025-06-20T22:58:58.502Z","ad50eacb-76dc-4f45-ad52-07d21d579b1c",[],[],{"_40":1329,"_128":1330,"_130":1331,"_132":1332,"_134":-5,"_13":-5,"_120":1333,"_122":136,"_25":1334,"_138":-5,"_139":1335,"_141":1336},"Realtime audiences | GrowthLoop Docs","realtime-audiences-growthloop-docs","https://docs.growthloop.com/docs/realtime-exports","## Real-time Audience Exports\n\nLearn how to export audiences in real-time as your data changes.\n\n> 📘\n> \n> Real-time Audience Exports are only available for audiences built on a **Snowflake** source connection. If your account is connected to Snowflake, you can enable real-time syncing to destinations the moment your data updates.\n\nMost marketing campaigns work well with audiences that update daily or hourly. But when the goal is to respond to customer behavior in the moment - like personalizing a webpage or sending a triggered message - hourly refreshes simply aren’t fast enough.\n\nThat’s why GrowthLoop now supports **Real-time Audience Exports**, allowing you to sync audiences to destinations the moment your data updates.\n\nHere are a few examples of where real-time exports shine:\n\n* A customer logs in, and you want to immediately suppress them from seeing a “Sign up” ad.\n* A shopper makes a purchase, and you want to trigger a cross-sell campaign right away.\n* Someone adds a product to their cart, and you want to retarget them within minutes, not hours.\n\nIn all of these use cases, waiting for the next hourly export means missed opportunities. GrowthLoop’s real-time exports are built to close that gap.\n\n1. **Customer Data is Updated**: A customer performs an action - like logging in or making a purchase - and the event is ingested into your Data Cloud (e.g., added to a Snowflake table).\n2. **Audience Membership Updates**: Your audience query, powered by GrowthLoop, detects the change and recalculates in real-time.\n3. **Export is Triggered Immediately**: Any new or removed audience members are sent to the destination through a low-latency queue—no waiting, no batch delays.\n\n![](https://files.readme.io/bcdf030be8dc01663e9a4645fcca567c856aa8c06e6837ace3a5ab19e0046123-realtime_image2.png)\n\nSetting up a real-time export in GrowthLoop is easy - as long as the following conditions are met:\n\n* ✅ You are using a Dataset Group on a **Snowflake** source connection\n* ✅ The audience does not include or exclude other audiences\n* ✅ You are exporting to a destination that supports real-time exports\n\nOnce those are in place:\n\n1. Navigate to the **Audience** you would like to export.\n2. Click **Export**.\n3. Select a **Destination**.\n4. Choose your **Match Fields** and **Personalization Fields**.\n5. Under **Export Frequency**, select **Real-time**.\n6. Click **Save**.\n\n> 👍\n> \n> Your audience will now sync in real-time as soon as the underlying data updates.\n\nReal-time exports allow marketers to move at the speed of their customers. By syncing audience changes as they happen, you can deliver personalized, timely experiences that drive results - and GrowthLoop makes it easier than ever.\n\n> 📘\n> \n> Contact your solutions architect at [support@growthloop.com](mailto:support@growthloop.com) for details on enabling **Real-time Exports** in your organization.\n\nUpdated 23 days ago\n\n* * *","2025-06-20T22:58:16.946Z","bc87a1b5-486c-4f0c-b3bb-8f85a6d206a7",[],[],{"_40":1338,"_128":1339,"_130":1340,"_132":1341,"_134":-5,"_13":-5,"_120":1342,"_122":136,"_25":1343,"_138":-5,"_139":1344,"_141":1345},"Real-Time Events in Journeys | GrowthLoop Docs","real-time-events-in-journeys-growthloop-docs","https://docs.growthloop.com/docs/real-time-journeys","Learn how to set up and launch real-time journeys to engage users instantly based on live event data\n\nIn this guide, we’ll walk through how to set up a real-time journey. Real-time journeys enable **dynamic, event-driven engagement** based on live data.\n\nBefore you begin, make sure you have:\n\n* **Apache Kafka** for event streaming ([learn more here](https://kafka.apache.org/intro)). Support for SQS and Pub/Sub will be added in the future.\n* **SendGrid** or **Salesforce Marketing Cloud (SFMC)** for email marketing (currently, these are the only real-time destinations supported).\n* **Real-time events enabled** in your org. If you don’t see this, contact your GrowthLoop rep to enable it.\n\n1. Log into **GrowthLoop** and go to the **Organization** page.\n2. Open the **Source Connections** tab and click **New Source Connection**.\n3. In the modal, select **Kafka**.\n4. Fill out the required details for the event queue connection:\n\n| Field Name | Required | Description | Example | Notes |\n| --- | --- | --- | --- | --- |\n| **Name** | ✅ Yes | A unique name to identify this Kafka connection. | `ProductionKafkaCluster`, `OrdersEventBroker` | Must be unique across connections. Used for display and reference. |\n| **Description** | ❌ No | Add context about the connection. | `Kafka cluster for production events` | Helpful for documentation/debugging. |\n| **Bootstrap Servers** | ✅ Yes | Comma-separated list of broker addresses. | `kafka-1.company.com:9092,kafka-2.company.com:9092` | At least one must be reachable. |\n| **Topic Name** | ✅ Yes | Kafka topic the consumer will subscribe to. | `user-signups`, `order.created` | Must already exist in the cluster. |\n| **Group ID** | ❌ No | Consumer group ID. | `signup-event-workers` | Auto-generated if left blank. |\n| **Security Protocol** | ✅ Yes | Defines communication/security protocol. | — | Common: `PLAINTEXT`, `SSL`, `SASL_SSL`. |\n| **Mechanism** | ⚠️ Conditional | Required if using SASL. | `PLAIN`, `SCRAM-SHA-256` | Must match Kafka server config. |\n| **Username** | ⚠️ Conditional | SASL username. | — | Provided by Kafka admin. |\n| **Password** | ⚠️ Conditional | SASL password. | — | Keep secure. |\n\n5. Click **Create**. A test connection will run, and if successful, your new source connection will be saved.\n\n> 👍\n> \n> **Success**\n> \n> You’ve successfully configured a real-time source connection!\n\n6. In the side menu, go to **Datasets** and select the **Realtime Events** tab.\n7. Click **New Realtime Event**.\n8. Fill out the event registration form:\n\n| Field Name | Required | Description |\n| --- | --- | --- |\n| **Event Source** | ✅ Yes | Select the real-time source connection (e.g., `ProductionKafkaCluster`). |\n| **Event Name** | ✅ Yes | A human-readable label for this event (e.g., `UserSignup`, `OrderPlaced`). |\n| **Path to Event** | ✅ Yes | Field path in the Kafka message to inspect (supports dot notation, e.g., `user.status.type`). |\n| **Event Value** | ✅ Yes | Value in the field above that triggers the event (e.g., `signup`). Messages without this value are ignored. |\n| **Register Event Schema** | ✅ Yes | JSON Schema describing the event payload for validation and field extraction. |\n\n9. Click **Save**.\n\n> 👍\n> \n> **Success**\n> \n> You’ve successfully created a real-time event!\n\n10. Switch to the **Dataset Group** tab.\n11. Select your Dataset Group, then open the **Realtime Events** tab.\n12. Click **Add Realtime Event**.\n13. In the modal, select the event you created.\n14. Map the real-time field to your dataset’s primary key.\n\n15. In the side menu, go to **Journeys** and click **New Journey**.\n16. In setup, choose **Realtime Journey** as the type.\n17. Select the Dataset Group with your registered event.\n18. From **Select Realtime Event**, choose your event.\n19. Configure the rest of the journey and click **Continue**. You’ll see a real-time entry node appear on the canvas with a lightning icon.\n20. Next, drag a **Criteria** node onto the canvas and filter users by event fields (e.g., event type, attributes).\n21. Then, drag a **Destination** node and choose a real-time destination (SendGrid or SFMC).\n\n> 📘\n> \n> **Note**\n> \n> The fields available in real-time destination node are sourced from the real-time event message schema and can be used for email recipient selection and template personalization.\n\n22. Click **Publish** to activate the journey.\n\n> 👍\n> \n> **Success**\n> \n> You’ve successfully created a real-time journey!\n\n* * *\n\n> 📘\n> \n> **Need help?**\n> \n> If you run into issues with Real-Time Journeys, reach out to us at [support@growthloop.com](mailto:support@growthloop.com).\n\nUpdated 23 days ago\n\n* * *","2025-10-23T18:21:15.685Z","730e2607-678f-4ad2-970d-0414ba776344",[],[],{"_40":1347,"_128":1348,"_130":1349,"_132":1350,"_134":-5,"_13":-5,"_120":1351,"_122":136,"_25":1352,"_138":-5,"_139":1353,"_141":1354},"Reddit Ads","reddit-ads","https://docs.growthloop.com/docs/reddit-ads","Learn how to connect and send audiences to Reddit Ads\n\nIn this article, we'll guide you through connecting **Reddit Ads** to GrowthLoop and exporting your audiences to the destination.\n\n**Reddit Ads** is an advertising solution that enables brands to reach highly engaged communities through targeted, interest-based placements across Reddit’s vast network of conversations.\n\n> 📘\n> \n> Your Reddit Ads Account must be whitelisted for `Custom Audience API` access. If it isn’t, please reach out to your Reddit rep to request access.\n\n* You’ll need a registered **Reddit Ads account**. If you don't have one yet, fill out this [form](https://ads.reddit.com/register/) to create one!\n* You'll also need your **Ad Account ID**. To find it, go to _Business Manager > Assets > Ad Accounts_. You’ll see all ad accounts linked to your business, with IDs listed under each name — they typically start with `a2_`.\n\n1. Log into **GrowthLoop** and click the **Destinations** tab on the left sidebar.\n \n2. Then click **New Destinations** on the upper right side.\n \n3. Next, search for **Reddit Ads** in the destination modal and click **Add Reddit Ads**.\n \n4. You’ll be redirected to Reddit’s **Request for Permission** page. Click **Allow** to grant GrowthLoop access to your Reddit Ads account.\n \n5. After granting permission, you'll be redirected back to GrowthLoop. Fill out the required fields in the modal and click **Create**:\n \n 1. `Destination`: Enter the name you want to give the destination.\n 2. `Sync Frequency`: Select a default export frequency to the destination.\n 3. `Business Account`: Select the business account from the drop-down menu where you want to export your audiences.\n 4. `Ad Account`: Enter the ad account ID linked to the selected business. To find it, go to _Business Manager > Assets > Ad Accounts_. You’ll see all ad accounts linked to your business, with IDs listed under each name — they typically start with `a2_`.\n\n6. Navigate to your list of audiences by clicking the **Audiences** tab on the left sidebar.\n7. Choose an existing audience or create a new one. Need help creating? Click [here](https://docs.growthloop.com/docs/create-an-audience) to learn how!\n8. Once created, click the **Export** button on the upper right side.\n9. Search for **Reddit Ads** in the export modal and then click **Select**.\n10. Map one of the following user identifiers under **Configure Match Field Settings**: `Email Address`, `Mobile Ad ID (MAID)`. After mapping, click **Next**.\n11. Configure your export settings:\n 1. `Export Name`: Automatically populated with your audience name for easy identification in the destination.\n 2. `Campaign Type`: Choose between a `One Time` export or `Ongoing` basis.\n 3. `Custom Audience Status`: Choose between `New` or `Existing`.\n 1. `New` (default): Creates a new custom audience in Reddit Ads using the name provided, and adds the users from your GrowthLoop audience.\n 2. `Existing`: When selected, a drop-down labeled `Select Custom Audience` will appear, allowing you to choose an existing Reddit Ads audience to add the users from your GrowthLoop audience into.\n 4. `Export Schedule`: Set the `Frequency`, `Start Date`, `End Date`, and specific `Days of the Week`.\n12. Finally, click **Export** to send the audience to **Reddit Ads**!\n\n> 👍\n> \n> You have successfully exported an audience!\n\nTo view your audience, log in to Reddit Ads and navigate to the **Audience Manager** section.\n\n![](https://files.readme.io/9db7c8b8bdc5c0cf0713aff92366981bd44bb212941ba3ed5fd590bb50276bb5-image_-_2025-05-15T103919.144.png)\n\n> 📘\n> \n> Experiencing any issues when connecting and/or exporting to **Reddit Ads**? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and we’ll be in touch shortly to help resolve the matter!\n\nUpdated about 1 month ago\n\n* * *","2025-06-20T22:58:59.372Z","b47b9879-1cd5-49a2-84a3-23a7baffb731",[],[],{"_40":1356,"_128":1357,"_130":1358,"_132":1359,"_134":-5,"_13":-5,"_120":1360,"_122":136,"_25":1361,"_138":-5,"_139":1362,"_141":1363},"Role Management","role-management","https://docs.growthloop.com/docs/role-management","Learn how to manage user permissions and roles in GrowthLoop.\n\nIn this article, you'll learn what types of custom roles can be created in GrowthLoop for permission management. You are able to design specific roles for your organization with granular permissions on datasets, audiences, and other objects within GrowthLoop.\n\nBy default, GrowthLoop has three defined roles within an organization:\n\n* `User Role`:\n * **Create Audiences:** User can create audience\n * **Edit Audiences:** User can edit audiences (Audiences that are shared with them as editor)\n * **Delete Audiences:** User can delete audiences (Audiences that are shared with them as editor)\n * **View Audience:** User can view audience (Audiences that are shared with them as viewer or editor)\n * **List Audiences:** User can view list of all audiences (Audiences that are shared with them as viewer or editor)\n * **Create Export:** User can export audiences (Audiences that are shared with them as editor)\n * **Update Exports**: User can update Exports ( Audiences that are shared with them as editor)\n * **Create Destination**: User can create Destinations\n * **Delete Destination**: User can delete Destinations\n * **Create Studio**: User can create audiences in studio\n * **Create Journey**: User can create journeys\n * **Update Journeys**: User can update journeys\n * **Delete Journeys**: User can delete journeys\n * **Create Syncs**: User can create syncs\n * **Update Syncs**: User can update syncs\n * **View Activity**: Admins can view activity across audiences and syncs in central dashboard\n* `Admin role`\n * Admin Role has all the permissions of User Role.\n * In addition, it has permissions to:\n * **Create Datasets**: Admin can create Datasets\n * **List Datasets**: Admin can view a list of all Datasets\n * **View Dataset**: Admin can view details of a specific dataset\n * **Update Dataset**: Admin can update Datasets\n * **Create Dataset Groups**: Admin can create Dataset Groups\n * **List Dataset Groups**: Admin can view a list of all Dataset Groups\n * **View Dataset Group**: Admin can view a specific Dataset Group\n * **Update Dataset Groups**: Admin can update Dataset Groups\n * **PII Exports**: Admin can use fields labeled as PII in exports for personalization of marketing messages\n * **List Teams**: Admin can view a list of all teams in organization\n * **Edit Teams**: Admin can add or remove users from teams\n * **List Users**: Admin can view a list of all users in organization\n * **Review Audiences**: Admins can review and approve audiences for export\n * **Refresh Source Connection**: Admins can refresh Source Connection\n * **Create Sources**: Admin can add source ingests to Data Cloud\n * **List Sources**: Admin can view list of all source ingests\n* `Owner Role`\n * Owner Role has all the permissions of User Role and Admin Role.\n * In addition, it has permissions to:\n * **Create Invites**: Owner can invite users to join organization.\n * **List Invites**: Owner can see list of all invites to organization.\n * **Create Storage**: Owner can set external storage configuration for exports.\n * **Update Notifications**: Owner can set who in the organization receives notifications.\n * **Update Share Settings**: Owner can set default audience share settings for organization.\n * **Create Source Connection**: Owner can create source connection for organizatoin.\n * **List Source Connections**: Owner can view list of all source conenctions.\n * **Update Source Connections**: Owner can assign Source Connections to specific teams and modify logging settings.\n\n> 📘\n> \n> Custom roles are available on GrowthLoop Enterprise plan\n\nGrowthLoop roles were designed to be completely customizable for enterprise teams. Many of our customers need high specific roles that fit their organization with granular permissioning. You are able to design an unlimited number of custom roles for users within your GrowthLoop `Organization`. These roles can then be assign to users to provide them with specific permissions.\n\nTo design a custom role simply select the permissions from GrowthLoops available list and give your role a name.\n\nOur team will configure the `Custom Role` for your organization in the GrowthLoop platform, and you will be able to assign your users with that specific role.\n\nTo update role assignments for users in your organization, simply follow these steps:\n\n1. Navigate to `Organization` page\n2. Click `Users` tab\n3. Select role next to user name, and the new role will automatically save for that user.\n\n![Update User Roles](https://files.readme.io/a00d55d-update_user_roles.png)\n\nUpdate user roles on Organization Management Panel\n\nIf you experience any issues or have any questions, please reach out to us at [support@growthloop.com](mailto:support@growthloop.com), and we’ll be in touch shortly!\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:31.551Z","7ec65036-a931-4395-8d9f-4237b90b9009",[],[],{"_40":1365,"_128":1366,"_130":1367,"_132":1368,"_134":-5,"_13":-5,"_120":1369,"_122":136,"_25":1370,"_138":-5,"_139":1371,"_141":1372},"Role Management & Permissions","role-management-permissions","https://docs.growthloop.com/docs/role-management-permissions","Learn how to manage user permissions and roles in GrowthLoop.\n\nIn this article, you'll learn what types of custom roles can be created in GrowthLoop for permission management. You are able to design specific roles for your organization with granular permissions on datasets, audiences, and other objects within GrowthLoop.\n\nBy default, GrowthLoop has three defined roles within an organization:\n\n| Action | User | Admin | Owner | Action Definition |\n| --- | --- | --- | --- | --- |\n| Create Audiences | ✅ | ✅ | ✅ | Creates audience |\n| Edit Audiences | ✅ | ✅ | ✅ | Edits audiences\\* |\n| Delete Audiences | ✅ | ✅ | ✅ | Deletes audiences\\* |\n| View Audiences | ✅ | ✅ | ✅ | Views audience\\* |\n| List Audiences | ✅ | ✅ | ✅ | Views list of all audiences\\* |\n| Create Templates | ✅ | ✅ | ✅ | Creates templates |\n| Edit Templates | ✅ | ✅ | ✅ | Edits templates |\n| Delete Templates | ✅ | ✅ | ✅ | Deletes templates |\n| Create Exports | ✅ | ✅ | ✅ | Exports audiences\\* |\n| Update Exports | ✅ | ✅ | ✅ | Updates Exports\\* |\n| CSV Exports | ❌ | ✅ | ✅ | Exports audiences to CSV (limited to < 300k records) |\n| Create Destination | ✅ | ✅ | ✅ | Creates Destinations |\n| Delete Destination | ✅ | ✅ | ✅ | Deletes Destinations |\n| Create Studio | ✅ | ✅ | ✅ | Creates audiences in studio |\n| Create Journey | ✅ | ✅ | ✅ | Creates journeys |\n| Update Journeys | ✅ | ✅ | ✅ | Updates journeys |\n| Delete Journeys | ✅ | ✅ | ✅ | Deletes journeys |\n| Create Syncs | ✅ | ✅ | ✅ | Creates syncs |\n| Update Syncs | ✅ | ✅ | ✅ | Updates syncs |\n| View Activity | ❌ | ✅ | ✅ | Views activity across audiences and syncs in central dashboard |\n| Create Datasets | ❌ | ✅ | ✅ | Creates Datasets |\n| List Datasets | ❌ | ✅ | ✅ | Views a list of all Datasets |\n| View Dataset | ❌ | ✅ | ✅ | Views details of a specific dataset |\n| Update Dataset | ❌ | ✅ | ✅ | Updates Datasets |\n| Create Dataset Groups | ❌ | ✅ | ✅ | Creates Dataset Groups |\n| List Dataset Groups | ❌ | ✅ | ✅ | Views a list of all Dataset Groups |\n| View Dataset Group | ❌ | ✅ | ✅ | Views a specific Dataset Group |\n| Update Dataset Groups | ❌ | ✅ | ✅ | Updates Dataset Groups |\n| PII Management | ❌ | ✅ | ✅ | Uses fields labeled as PII in exports for personalization of marketing messages |\n| List Teams | ❌ | ✅ | ✅ | Views a list of all teams in organization |\n| Edit Teams | ❌ | ✅ | ✅ | Adds or removes users from teams |\n| List Users | ❌ | ✅ | ✅ | Views a list of all users in organization |\n| Review Audiences | ❌ | ✅ | ✅ | Reviews and approves audiences for export |\n| Refresh Source Connection | ❌ | ✅ | ✅ | Refreshes Source Connection |\n| Create Sources | ❌ | ✅ | ✅ | Adds source ingests to Data Cloud |\n| List Sources | ❌ | ✅ | ✅ | Views list of all source ingests |\n| Create Invites | ❌ | ❌ | ✅ | Invites users to join organization |\n| List Invites | ❌ | ❌ | ✅ | Sees list of all invites to organization |\n| Create Storage | ❌ | ❌ | ✅ | Sets external storage configuration for exports |\n| Update Notifications | ❌ | ❌ | ✅ | Sets who in the organization receives notifications |\n| Update Share Settings | ❌ | ❌ | ✅ | Sets default audience share settings for organization |\n| Create Source Connection | ❌ | ❌ | ✅ | Creates source connection for organization |\n| List Source Connections | ❌ | ❌ | ✅ | Views list of all source connections |\n| Update Source Connections | ❌ | ❌ | ✅ | Assigns Source Connections to specific teams and modifies logging settings |\n| [User Activity Audit Logs](https://docs.growthloop.com/docs/user-activity-audit-logs) | ❌ | ✅ | ✅ | Visibility of actions taken by any user |\n\n\\*Audiences that are shared with them as editor\n\n> 📘\n> \n> Custom roles are available on GrowthLoop Enterprise plan\n\nGrowthLoop roles were designed to be completely customizable for enterprise teams. Many of our customers need high specific roles that fit their organization with granular permissioning. You are able to design an unlimited number of custom roles for users within your GrowthLoop `Organization`. These roles can then be assign to users to provide them with specific permissions.\n\nTo design a custom role simply select the permissions from GrowthLoops available list and give your role a name.\n\nOur team will configure the `Custom Role` for your organization in the GrowthLoop platform, and you will be able to assign your users with that specific role.\n\nTo update role assignments for users in your organization, simply follow these steps:\n\n1. Navigate to `Organization` page\n2. Click `Users` tab\n3. Select role next to user name, and the new role will automatically save for that user.\n\n![Update User Roles](https://files.readme.io/a00d55d-update_user_roles.png)\n\nUpdate user roles on Organization Management Panel\n\nIf you experience any issues or have any questions, please reach out to us at [support@growthloop.com](mailto:support@growthloop.com), and we’ll be in touch shortly!\n\nUpdated 5 months ago\n\n* * *","2025-06-20T22:58:44.773Z","524ca10c-3d52-47a6-ade8-c9c1f0f78a5d",[],[],{"_40":1374,"_128":1375,"_130":1376,"_132":1377,"_134":-5,"_13":-5,"_120":1378,"_122":136,"_25":1379,"_138":-5,"_139":1380,"_141":1381},"Salesforce","salesforce","https://docs.growthloop.com/docs/salesforce","Salesforce is a leading cloud-based software for customer relationship management (CRM), empowering companies to better connect with leads and established customers alike. GrowthLoop amplifies the power of CRM by allowing you to segment these individuals across any metric in your data warehouse, paving the way for more relevant and targeted campaigns. This article outlines the steps necessary to set up Salesforce as a GrowthLoop destination and begin exporting audiences for activation. \nBefore connecting Salesforce to the application, we will walk through one requirement:\nCreating a Security Token\nConnecting Salesforce as an audience destination requires a security token specific to your Salesforce account. If you do not know your security token, you will need to reset it using the steps below. If you know your token, skip to Connecting Salesforce as a Destination. \nLog in to Salesforce with your username and password. From the home screen, click your User Icon at the top right corner and select Settings. \nType “token” into the Quick Find bar in the left rail and click Reset My Security Token. \nClick Reset Security Token. A new token will be sent to the email address associated with your Salesforce account. \nOnce you know your security token, you’re ready to connect Salesforce as an audience destination! \nSelect Destinations from the left rail of your GrowthLoop home screen. \nClick New Destination on the top right. \nScroll down to the CRM section of the pop-up window and click Add Salesforce Audience. \nComplete all Destination Info and Credentials fields (see below for assistance), then click Create.\nDestination Name: A custom name for your destination. \nSync Frequency: The frequency at which GrowthLoop will export audiences to your destination (hourly or daily). \nUsername: Your Salesforce username.\nPassword: Your Salesforce password.\nSecurity Token: Your Salesforce security token.\nDev Environment: Check this box if your Salesforce destination is a sandbox (development) environment. If you aren’t sure, take a look at the Salesforce URL that you use to log in. If this URL begins with “test,” i.e. test.salesforce.com, check the box. If not, leave it empty. \nOnce you’ve set up Salesforce as a destination and created an audience, you can begin exporting!\nOpen the target audience and click Export. \nFind your Salesforce destination and click Activate. \nIn the modal window, specify how GrowthLoop should match audience members to your Salesforce leads, contacts and accounts. Each match condition unlocks a different set of actions you can apply to matching and non-matching profiles in Salesforce. \nMatch on Contacts and Leads: Look for matches across all contacts and leads in Salesforce. \nMatch on Account: Look for matches with accounts in Salesforce. \nMatch on Leads Only: Look for matches only with Salesforce leads, ignoring contacts. \nCreate Campaign in Salesforce for each GrowthLoop Audience: Selecting Yes will create a campaign for this audience in your Salesforce instance. To do so, you must have Marketing User Privileges assigned to your Salesforce username. \nWhen matching on contacts and leads, you have an extensive set of options for customizing your audience export to Salesforce.\nMatching Contacts\nYou can filter all contact matches across opportunity type, owner, and stage, applying a specific action to only contacts who meet these criteria. Available actions include adding tasks, opportunities, and activities. You have the option of assigning this action to either the opportunity owner (by checking Copy opportunity owner for this task) or specifying a different owner’s email address.\nYou can also choose a separate action to apply to matching contacts who do not meet your opportunity criteria. \nMatching Leads\nAs with contacts, there are a variety of actions available for matching leads, ranging from updating the lead to converting it to an account and contact. \nNon-Matching Contacts or Leads \nFinally, you can also take action on any audience member who does not match an existing contact or lead in Salesforce. You can create a new lead or contact (among others) by identifying the fields in your data that correspond with an individual’s company, name and contact information. \nChoosing Match Fields\nFinally, choose the data identifier that will match your GrowthLoop audience members to your Salesforce leads and contacts. This is typically a Contact ID or email address. \nSelecting “Match on Account” allows you to match on Salesforce account, rather than contact or lead. As with contacts and leads, you can apply actions to accounts right from GrowthLoop! \nMatching Accounts\nYou can filter all account matches across opportunity type, owner, and stage, applying a specific action to only accounts that meet these criteria. Available actions include adding tasks, opportunities, and activities. You can assign this action to either the opportunity owner (by checking Copy opportunity owner for this task) or specifying a different owner’s email address.\nYou can also choose a separate action to apply to any contacts who do not match your criteria. \n— THERE IS A BUG IN THE UI THAT NEEDS TO BE FIXED BEFORE I CAN COMPLETE THIS SECTION — \nSelecting “Match on Leads Only” allows you to match audience members to Salesforce leads only, ignoring Salesforce contacts. \nMatching Leads\nFor matching leads, you can add a task, convert the lead and create an opportunity, or do nothing. \nNon-Matching Leads\nFor audience members that do not match an existing lead, you can create new Salesforce leads or contacts by specifying the fields in your data that correspond with members’ companies, names and contact information. \nNon-Matching Leads\nFor audience members that do not match an existing lead, you can create new Salesforce leads or contacts by specifying the fields in your data that correspond with members’ companies, names and contact information. \n— THERE IS A BUG IN THE UI THAT NEEDS TO BE FIXED BEFORE I CAN COMPLETE THIS SECTION —\nUpdated 3 months ago","2024-03-20T21:02:29.250Z","28db5a49-3ae1-4f4c-b8ca-8cd42df2ee08",[],[],{"_40":1383,"_128":1384,"_130":1385,"_132":1386,"_134":-5,"_13":-5,"_120":1387,"_122":136,"_25":1388,"_138":-5,"_139":1389,"_141":1390},"Send audiences to Viant digital advertising | GrowthLoop Docs","send-audiences-to-viant-digital-advertising-growthloop-docs","https://docs.growthloop.com/docs/viant","# Send audiences to Viant digital advertising\n\nLearn how to connect and send audiences to Viant\n\nIn this article, we'll walk you through the process of connecting Viant to GrowthLoop and exporting your audiences to the destination for programmatic advertising.\n\n* Ensure you have an active Viant account - click [here](https://www.viantinc.com/contact/) to schedule a call if you don't!\n\n1. Log into **GrowthLoop** and click the **Destinations** tab on the left sidebar.\n \n2. Then click **New Destinations** on the upper right hand-side.\n \n3. Next, search for **Viant** in the destination modal and click **Add Viant**.\n \n4. In the modal, please **select/insert** the following information:\n \n * **Destination Name:** This is how the destination will be named and referred to in to the app going forward. It is helpful to make this name “marketer friendly” so everyone on your team knows it’s purpose.\n * **Sync frequency**: This is the default frequency audiences will be synced to a destination. Marketers can always change the frequency of an export, but this sets the default.\n * **Username:** Please contact your Viant rep to obtain a username.\n * **Password:** Please contact your Viant rep to obtain a password.\n\n> 📘\n> \n> **Note**\n> \n> The username and password credentials are Viant partner credentials specific to GrowthLoop and your Viant account, these are not regular Viant user credentials.\n\n5. Go ahead and select **Create**, and you will see **Viant** appear in your Destinations table!\n\n6. Navigate to your list of audiences by clicking the **Audiences** tab on the left sidebar.\n7. Choose an existing audience or create a new one. Need help creating? Click [here](https://docs.growthloop.com/docs/create-an-audience) to learn how!\n8. Once created, click the **Export** button on the upper right side.\n9. Search for **Viant** in the export modal and then click **Select**.\n10. Map one of the following user identifiers under **Configure Match Field Settings**:\n 1. `Email Address` (Required)\n 2. `Physical Address`\n 3. `IP`\n 4. `Mobile ID`\n 5. `Cookie ID`\n 6. `UID2`\n 7. `RampID`\n 8. `ID5`\n 9. `Transaction ID`\n 10. `Sales Amount`\n\n> 📘\n> \n> **Note**\n> \n> If you're mapping the `Physical Address`, ensure that your data adheres to postal service format (e.g., 1465 N Larrabee St #27a, Chicago, IL 60610, USA)\n\n11. After mapping at least `Email Address`, click **Next**.\n12. Next, configure your export settings:\n 1. `Export Name`: Automatically populated with your audience name for easy identification in the destination.\n 2. `Campaign Type`: Choose between a `One Time` export or `Ongoing` basis.\n 3. `Segment Name (Required)`: The name of the segment.\n 4. `Adelphic / Viant AID (Required)`: The Adelphic / Viant AID associated with the segment.\n 5. `Segment ID` (Required): The unique identifier for the segment.\n 6. `Segment ID Type` (Optional): The type of segment.\n * Userpool: Used when you want to send the data to an existing Viant DSP userpool\n * Taxonomy: Used when you want to send the data to an existing Viant DSP taxonomy segment\n * Third Party: Used when you want it to go to Viant DSP taxonomy that is 3rd party\n 7. `Export Schedule`: Set the `Frequency`, `Start Date`, `End Date`, and specific `Days of the Week`.\n13. Lastly, click **Export**, and you're done!\n\n> 👍\n> \n> **Success** You have successfully exported an audience!\n\n> 📘\n> \n> **Note**\n> \n> Audience data may take up to 24 hours to populate.\n\nTo view your audience, log in to Viant and navigate to the **Identity Management** section.\n\n![](https://files.readme.io/e82d86aa73f97f000e7d7f7750b8dd040fd111d3320dfcfc08c5e90998a9618d-image.png)\n\n> 📘\n> \n> Note\n> \n> Experiencing any issues when connecting and/or exporting to **Viant**? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and we’ll be in-touch shortly to help resolve the matter!\n\n \n\nUpdated about 1 month ago\n\n* * *","2025-06-20T22:57:59.246Z","26eb93b9-1a96-4b7d-b5ba-51c1475f9b0d",[],[],{"_40":1392,"_128":1393,"_130":1394,"_132":1395,"_134":-5,"_13":-5,"_120":1396,"_122":136,"_25":1397,"_138":-5,"_139":1398,"_141":1399},"SendGrid","sendgrid","https://docs.growthloop.com/docs/sendgrid","Learn how to connect and send audiences to SendGrid\n\nIn this article, we'll guide you through connecting SendGrid to GrowthLoop and exporting your audiences to the destination.\n\n* Make sure you have a SendGrid account. If not, you can create one [here](https://signup.sendgrid.com/)!\n* Make sure your **API Key** is handy and it has full access or at least Marketing permissions. To create one,\n 1. **Log in to your account**.\n 2. Go to **Settings** from the left-hand navigation panel.\n 3. Select **API Keys**.\n 4. Click **Create API Key**.\n 5. Choose **Full Access** (preferred) or **Restricted Access** with Marketing permissions.\n 6. Click **Create & View** to generate your API Key.\n 7. **Copy your API Key** and store it securely, as it won't be displayed again for security reasons.\n\n1. Log into **GrowthLoop** and click the **Destinations** tab on the left sidebar.\n \n2. Then click **New Destinations** on the upper right side.\n \n3. Next, search for **SendGrid** in the destination modal and click **Add SendGrid**.\n \n4. Enter the required information in the modal, then click **Create**.\n \n 1. **Destination Name**: This is how the destination will be named and referred to in the app going forward.\n 2. **Sync Frequency**: This indicates how frequently audiences will be synced to the destination.\n 3. **API Key**: A unique string of characters that serves as an authentication credential for GrowthLoop to create, update, and manage contact lists. Follow the steps outlined above to learn how to create one.\n\n5. Navigate to your list of audiences by clicking the **Audiences** tab on the left sidebar.\n \n6. Choose an existing audience or create a new one. Need help creating? Click [here](https://docs.growthloop.com/docs/create-an-audience) to learn how!\n \n7. Once created, click the **Export** button on the upper right side.\n \n8. Search for **SendGrid** in the export modal and then click **Add SendGrid**.\n \n9. Map one of the following fields under **Configure Match Field Settings**: **Email**, **Phone Number**, **External ID**, or **Anonymous ID**. SendGrid requires at least one user identifier for each export. Click **Next**.\n \n10. Configure your export settings:\n \n * **Export Name**: Automatically populated with your audience name for easy identification in the destination.\n * **Campaign Type**: Choose between a one-time export or ongoing basis.\n * **List Status**: Choose between **new** or **existing**.\n * For new lists, it will use the audience name and add records to it.\n * For existing lists, input the List ID to add records to it. To find it, navigate to a marketing list in SendGrid. The list ID is the last part of the URL.\n * **Export Schedule**: Set the frequency, start date, end date, and specific days of the week.\n11. Lastly, click **Export**. Congrats on successfully exporting an audience to SendGrid! To view your audience, log in to your account, click the **Marketing** tab, and select **Contacts**.\n \n ![](https://files.readme.io/4c9803f-image.png)\n\n \n\n> 📘\n> \n> Experiencing any issues when connecting and/or exporting to **SendGrid**? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and we’ll be in touch shortly to help resolve the matter!\n\nUpdated 5 months ago\n\n* * *","2025-06-20T22:59:01.896Z","69e35a7d-2ce5-4c68-9aa3-4eddca7c58e6",[],[],{"_40":1401,"_128":1402,"_130":1403,"_132":1404,"_134":-5,"_13":-5,"_120":1405,"_122":136,"_25":1406,"_138":-5,"_139":1407,"_141":1408},"Send Slack Alerts for your GrowthLoop Audiences and Journeys","send-slack-alerts-for-your-growthloop-audiences-and-journeys","https://docs.growthloop.com/docs/slack-alerts","Learn how to manage user permissions and roles in GrowthLoop.\n\nIn this article, you'll learn how to setup Slack Alerts for audiences and syncs in GrowthLoop. These are helpful to notify your team of successes and failures in particular audiences, syncs, and journeys. It is also helpful to ensure your dataset health and destination connections are always operational.\n\nThe easiest way to send notifications to your selected channels is with Slack's email integration. Every Slack channel has an email address. Any email sent to the channel's address automatically appears as a message in that channel.\n\nSlack implemented this integration method to remove the need for giving software providers (like GrowthLoop) access to your Slack organization.\n\nHere is how you get it setup:\n\n1. Navigate to Slack\n \n2. Navigate to the Slack channel where you would like GrowthLoop to send notifications\n \n3. Click on the channel name to open up the Slack Channel Information panel\n \n ![](https://files.readme.io/b53af27-Screenshot_2024-02-28_at_4.48.00_PM.png)\n4. Click on Integrations\n \n ![](https://files.readme.io/0b70a68-image.png)\n5. View the Slack channel's email address\n \n ![](https://files.readme.io/4101a48-Screenshot_2024-02-28_at_4.48.22_PM.png)\n6. Select \"Get Email Address\"\n \n ![](https://files.readme.io/ccb2c95-Screenshot_2024-02-28_at_4.48.30_PM.png)\n7. Copy the Slack channel's email address\n \n ![](https://files.readme.io/4a451bf-Screenshot_2024-02-28_at_4.48.39_PM.png)\n8. Navigate to notifications in GrowthLoop and paste in the email address of the Slack channel for the notifications you would like to be sent there.\n \n\n![](https://files.readme.io/38d3b77-Slack_Alerts.png)\n\nYour Slack channel will now receive any new notifications directly from GrowthLoop.\n\nIf you experience any issues or have any questions, please reach out to us at [support@growthloop.com](mailto:support@growthloop.com), and we’ll be in touch shortly!\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:32.487Z","f7861dcd-ed18-4a72-96e2-4de1f82e8f59",[],[],{"_40":1410,"_128":1411,"_130":1412,"_132":1413,"_134":-5,"_13":-5,"_120":1414,"_122":136,"_25":1415,"_138":-5,"_139":1416,"_141":1417},"Send targeted audiences to Hubspot | GrowthLoop Docs","send-targeted-audiences-to-hubspot-growthloop-docs","https://docs.growthloop.com/docs/hubspot-destination","# Send targeted audiences to Hubspot\n\nLearn how to set up Hubspot as a destination so you can start exporting audiences to it.\n\nThis article outlines the steps necessary to set up Hubspot as a GrowthLoop destination and begin exporting audiences for activation.\n\nTo connect the GrowthLoop application to Hubspot, you must have an Hubspot account. You will be prompted to log in or be prompted to connect GrowthLoop if you are already logged in in your browser.\n\n1. When you sign into the GrowthLoop Platform, navigate to the **Destinations** tab on the left sidebar and click **New Destination** in the top right corner .\n \n ![](https://files.readme.io/da15910-Untitled.png)\n2. When the **Select Destination** window pops up, type HubSpot into the Search Bar to find HubSpot and click **Add Hubspot Audience**.\n \n ![](https://files.readme.io/48e57e5-Untitled_1.png)\n3. Clicking **Add HubSpot Audience** will take you to the HubSpot login page where you can input your credentials and click **Log in**.\n \n ![](https://files.readme.io/a7b1f46-Untitled_2.png)\n4. Choose the account you’d like to connect to GrowthLoop and click **Choose Account**.\n \n ![](https://files.readme.io/906a685-Untitled_3.png)\n5. Then click **Connect app**.\n \n ![](https://files.readme.io/7d947de-Untitled_4.png)\n6. After this you will be prompted to select/insert the following information\n \n ![](https://files.readme.io/1452832-Untitled_5.png)\n 1. **Destination name:** This is a friendly name for the destination, used to refer to it within the app.\n 2. **Sync Frequency:** The default frequency for syncing audiences to a destination (Hourly or Daily).\n 3. **Access Token:** Automatically populated by Hubspot\n 4. **Refresh Token:** Automatically populated by Hubspot\n7. Once all required information is provided, the **Create** button will turn blue. Click it to finalize the destination.\n \n\n**Exporting to the destination**\n\n1. Navigate to the Audiences section in the left sidebar. From there, you can either select an existing audience or create a new one. (Click [here](https://docs.growthloop.com/docs/create-an-audience) to learn how!)\n \n ![](https://files.readme.io/5d18273-6edf2f7-image.png)\n2. After selecting or creating your audience, click **Export Audience**.\n \n ![](https://files.readme.io/aa7c10d-6b1cca1-Screen_Shot_2023-04-30_at_9.26.44_PM.png)\n3. In the **Create Export** view, search for your **Hubspot** Destination and click **Select**.\n \n4. Then in the **Export Settings** tab, configure your desired **Campaign Type, Export Schedule,** and \\***\\*the** Personalization Fields\\*\\* that will be exported to Hubspot as new custom properties.\n \n ![](https://files.readme.io/2fc28b2-Untitled_6.png) ![](https://files.readme.io/f687c37-Untitled_7.png)\n5. Next, configure your match fields in the **Match Fields** tab. Currently, only **Email Address** is supported, with potential for more options in the future!\n \n ![](https://files.readme.io/5d3e7df-9df3243-image.png)\n6. Lastly, click **Export**, and you're done! You can double check a successful export to **Hubsport** by navigating to your audience viewer **Exports** tab within your GrowthLoop app to view the activity tracker and make any scheduling changes you may need.\n \n ![](https://files.readme.io/56ab602-Untitled_8.png)\n7. To see your audience in **Hubspot**, navigate to the **CRM** tab in the sidebar and click **Lists**. GrowthLoop exports audiences as a Contact object type and any personalization fields sent as part of the export can be found under the Flywheel Contact Properties group and will be named with the following scheme `Flywheel Personalization - flywheel_personalization_[field name]` .\n \n\n![](https://files.readme.io/f62ebe7-Untitled_9.png) ![](https://files.readme.io/f4b848a-Untitled_10.png)\n\nExperiencing any issues when connecting to HubSpot? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and we’ll be in-touch shortly to help resolve the matter!\n\nUpdated 5 months ago\n\n* * *","2025-06-20T22:58:42.692Z","b246e249-c6f7-4ffb-b0ed-2d42b75292cc",[],[],{"_40":1419,"_128":1420,"_130":1421,"_132":1422,"_134":-5,"_13":-5,"_120":1423,"_122":136,"_25":1424,"_138":-5,"_139":1425,"_141":1426},"Set Google Cloud Storage as a destination | GrowthLoop Docs","set-google-cloud-storage-as-a-destination-growthloop-docs","https://docs.growthloop.com/docs/google-cloud-storage","# Set Google Cloud Storage as a destination\n\nThis article outlines the steps necessary to set up a Google Cloud Storage bucket as a GrowthLoop destination and begin exporting audiences for activation. ##\n\nThis article outlines the steps necessary to set up a Google Cloud Storage bucket as a GrowthLoop destination and begin exporting audiences for activation.\n\n* Create a Google Cloud Storage service account and save its account key as a JSON file\n* Create a Google Cloud Storage bucket\n\nIf you already have a service account and have stored its key as a JSON file, you can skip to **Setting Google Cloud Storage as a Destination.**\n\nIn order to export to a Google Cloud Storage bucket, you must have a service account with permissions to manage that bucket. [Here](https://cloud.google.com/iam/docs/creating-managing-service-accounts#creating_a_service_account) are instructions for setting up a service account. Make sure to assign your service account the **Editor** role (available as one of Google Cloud Platform’s **Basic Roles**).\n\nJSON keys are files that allow external services like GrowthLoop to engage your service account. We generally recommend creating a new service account to connect GCS to the GrowthLoop application. If you already have a JSON key for your service account, skip to **Setting Google Cloud Storage as a Destination**. If you do not, you will need to create a new one using the steps below. Make sure to save your JSON key file in a safe and memorable place \\***\\*- this key is** not recoverable\\*\\*, and you will need to create another if you lose it. You have a limit of 10 keys per service account.\n\nTo create a key, you need to have administrative privilege over keys for your storage bucket. If you receive a permissions error during the key setup process, ask your Google Cloud administrator to either 1) provide you with key creation permissions, or 2) create the key themselves and provide you with the JSON.\n\nFirst, log in to your Google Cloud Platform account and search the name of your storage bucket in the **Search** bar at the top of the screen. _Note: Even if the dropdown says “No results,” press Enter and your bucket will appear on the next screen._\n\n![](https://files.readme.io/c1a3566-search_gcs.png)\n\nSelect your desired storage bucket.\n\n![](https://files.readme.io/043c1db-Untitled_1.png)\n\nClick **Permissions.**\n\n![](https://files.readme.io/83cd795-Untitled_2.png)\n\nScroll down to the list of **Permissions** and find the service account that is assigned storage privileges (in this case, the top one). You can tell which users are service accounts by looking for “gserviceaccount” in the **Principal** column. Copy or screenshot the name of this service account.\n\n![](https://files.readme.io/7e728ed140aaacca967fd18ae0d34faf6dddacc57a2a73089ce7ce46fd471915-image.png)\n\nIn the **Search** bar, type “Service Accounts” and select **Service Accounts** from the dropdown.\n\n![](https://files.readme.io/79add1d-gcs_service_accounts.png)\n\nFrom the list of service accounts, click into the one that matches the one you copied down from your storage bucket.\n\n![](https://files.readme.io/7850f95-gcs_service_account_selection.png)\n\nNavigate to **Keys.** Choose **Create New Key** from the **Add Key** dropdown.\n\n![](https://files.readme.io/9300b3b-gcs_service_account_keys.png)\n\nSelect **JSON** and click **Create.** The new key file will automatically download to your computer as a JSON file. Save it in a secure, memorable place.\n\n![](https://files.readme.io/03b4c8a-gcs_service_account_json_key.png)\n\nNow that you have a service account and service account key, you are ready to set Google Cloud Storage as a destination!\n\nSelect **Destinations** from the left rail of your GrowthLoop home screen.\n\n![](https://files.readme.io/fc3de81-destination_left_menu.png)\n\nClick **New** **Destination** on the top right.\n\n![](https://files.readme.io/d3d569c-new_destination.png)\n\nScroll down to the **Buckets** section and click **Add GCS**.\n\n![](https://files.readme.io/d9e487f-add_gcs_destination.png)\n\nA modal window will prompt you to fill out **Destination Info** and **Credentials**.\n\n![](https://files.readme.io/079de2d-gcs_destination_config.png)\n\n* **Destination Name:** A custom name for your destination.\n* **Sync Frequency:** The frequency at which GrowthLoop will export audiences to your destination (hourly or daily).\n* **Bucket:** The name of your Google Cloud Storage bucket.\n* **Credentials:** Copy and paste the entire contents of your JSON key file here.\n* **Columns to Export:** Columns that will be exported by default when you export an audience to GCS. Use the column names of the underlying datasets in your data warehouse. If you do not specify any column names, all columns will be exported by default.\n\nClick **Create.** You are now ready to begin exporting to your Google Cloud Storage destination! You can confirm that your Google Cloud Storage bucket is connected by clicking **Destinations** on the left rail.\n\n![](https://files.readme.io/d4ec0c2-gcs_destination_added.png)\n\nWhen exporting to Google Cloud Storage, you will be prompted select an **Export Type** and **Personalization Fields**\n\n![](https://files.readme.io/c3d59a0-gcs_destination_export.png)\n\n* **Export Type:** Choose between **Export All Records** and **Export Updates (Deltas).**\n * **Export All Records:** Each time your audience exports to GCS, a new record is created for every member of the audience.\n * **Export Updates (Deltas):** Each time your audience exports to GCS, a new record is only created for _new_ members of the audience.\n* **Personalization Fields:** By default, GrowthLoop will export only the columns specified during destination setup (called **Columns to Export**). If you would like to add any additional columns to your export, do so here.\n\nAfter exporting, a folder unique to your audience will appear in your Google Cloud storage bucket. This folder contains individual CSV files for each member of the audience.\n\n![](https://files.readme.io/f6ac360-gcs_audience_file.png)\n\nExperiencing any issues connecting to Google Cloud Storage as a destination? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and we’ll be in touch shortly!\n\nLooking to connect other sales and marketing destinations for audience activation? **[Click Here](https://www.growthloop.com/help-center-categories/destinations)** to find more information in our Help Center!\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:27.013Z","0e2d65ff-81f4-472b-ba3d-a6a504b8dc34",[],[],{"_40":1428,"_128":1429,"_130":1430,"_132":1431,"_134":-5,"_13":-5,"_120":1432,"_122":136,"_25":1433,"_138":-5,"_139":1434,"_141":1435},"Setting up an audience retention policy | GrowthLoop Docs","setting-up-an-audience-retention-policy-growthloop-docs","https://docs.growthloop.com/docs/audience-retention-policy","# Setting up an audience retention policy\n\nLearn how to set up retention policies for audience memberships stored in your data warehouse.\n\nIn this article, we'll walk you through what an `Audience Retention Policy` is, how it helps save on costs, and how to set it up in GrowthLoop.\n\nAn `Audience Retention Policy` defines how long audience memberships from each **export run** are stored in your warehouse before being deleted. An export run refers to the process of sending audience data from GrowthLoop to a destination. This data is kept to calculate deltas (changes between snapshots), which help track how your audience evolves over time.\n\nRetention policies ensure older audience memberships are automatically cleaned up, keeping your warehouse organized and cost-efficient. For example, data from campaigns that ended over a year ago may no longer be needed. Deleting these records after one year can save on storage costs while keeping recent, valuable data accessible.\n\n1. Navigate to the **Organization** page under **Settings**. Please note: you must have either **Admin** or **Owner** role access to proceed.\n2. Select the **Storage** tab and scroll down to find the **Logging to Warehouse** section.\n3. Open the **Retain** drop-down under **Audience Snapshots**.\n4. The drop-down will show a list of options ranging from **1 week** to **1 year**, with an additional option to store data **Forever**.\n5. Choose an option, such as **1 year**. Optionally, you can select a custom dataset to store your snapshots. By default, snapshots are written to the **audience\\_snapshots** dataset.\n6. Finally, click **Save** to apply the retention policy.\n\n> 👍\n> \n> You've configured your `Audience Retention Policy`!\n\nConfiguring retention policies in GrowthLoop is a simple yet powerful way to manage audience memberships in your warehouse. By implementing retention policies, you can save on data storage costs, keep your warehouse organized, and ensure that only the most relevant audience data is retained.\n\n> 📘\n> \n> Need further help with setting up retention policies? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and we'll be in touch shortly to help!\n\nUpdated 5 months ago\n\n* * *","2025-06-20T22:58:07.625Z","870dc6ca-d9ab-4599-94db-9d427d939873",[],[],{"_40":1437,"_128":1438,"_130":1439,"_132":1440,"_134":-5,"_13":-5,"_120":1441,"_122":136,"_25":1442,"_138":-5,"_139":1443,"_141":1444},"Set up a Sync from a source to a destination | GrowthLoop Docs","set-up-a-sync-from-a-source-to-a-destination-growthloop-docs","https://docs.growthloop.com/docs/syncs-overview","# Set up a Sync from a source to a destination\n\n## Overview\n\nLearn how to setup a Sync to a destination\n\nIn this article, you'll learn how to set up a Sync from your `Source` to a `Destination` in GrowthLoop. This is useful to add personalization signals directly in your marketing and sales platforms so you can easily send emails, push, and SMS with personalizations like `first name` `last name` and other attributes.\n\nWe recommend you use the`Syncs` only for `personalization signals`. If you use `Syncs` to push as much data as you can to all of your marketing and sales tools, you will create a large headache within your organization, and lose the core benefits of the composable marketing stack you have put in place.\n\n* **Column count:** Are you syncing more than 10 columns to a marketing destination? Syncing more than 10 fields at a time is a red flag for `data proliferation`.\n* **Targeting vs. Personalization:** Are you syncing fields for message personalization? Or are you syncing fields for use in targeting? Typically, messaging personalization only requires 10-20 commonly used fields and is a great use for `Syncs`. On the other hand, `Targeting` often requires the ability to filter customers on 100+ fields to reach the right audience. We strongly recommend not to use `Syncs` to port over 100s of fields to use another downstream tool for targeting. This causes `data proliferation` and increased costs in your SAAS tools.\n\nTo demonstrate how to set up your sync, we'll use Klaviyo as our destination and walk you through the details of setting a sync up.\n\nLearn how to send the latest user info from your Data Warehouse to Klaviyo. This will enable you to build more accurate customer profiles for precise targeting. Let's get started!\n\n1. To begin, sign into the GrowthLoop Platform and navigate to the Destinations tab on the left sidebar. Click New Destination in the top right corner.\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/653913926d2996605ad09338_Screenshot%202023-10-25%20at%209.04.33%20AM.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/653913926d2996605ad09338_Screenshot%202023-10-25%20at%209.04.33%20AM.png)\n\n‍\n\n2. In the Select Destination window that appears, just type Klaviyo into the search bar. Then, click Add Klaviyo.\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/653913adb803d2a9e4aec119_Screenshot%202023-10-25%20at%209.04.48%20AM.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/653913adb803d2a9e4aec119_Screenshot%202023-10-25%20at%209.04.48%20AM.png)\n\n3. In the window, please enter the following information to set up the connection to the destination.\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/653913bf6e5038f379437292_Screenshot%202023-10-25%20at%209.04.57%20AM.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/653913bf6e5038f379437292_Screenshot%202023-10-25%20at%209.04.57%20AM.png)\n\n* Destination Name**:** This is how the destination will be named and referred to in the app going forward.\n* Sync Frequency**:** Choose between Hourly or Daily to determine how frequently GrowthLoop exports audiences to Klaviyo.\n* API Key: Locate your API key in account settings or create one using Create API KEY if it doesn't exist. Keep in mind that only users with roles such as Owner, Admin, or Manager can view and create API keys.\n\n4. Once you've entered the information, click on Create. We'll check to make sure we have all the necessary permissions to send audience data to Klaviyo. If everything is in order, you'll now find the new Klaviyo Destination in your list of connected destinations.\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/653913e8ca705a4e6f899bcc_Screenshot%202023-10-25%20at%209.05.09%20AM.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/653913e8ca705a4e6f899bcc_Screenshot%202023-10-25%20at%209.05.09%20AM.png)\n\n1. To route the latest user info (e.g., email, phone, city) to Klaviyo, go to the Signals tab on the left sidebar and click New Signal Route in the top right corner.\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/65391402cb2f92884fccb896_Screenshot%202023-10-25%20at%209.05.41%20AM.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/65391402cb2f92884fccb896_Screenshot%202023-10-25%20at%209.05.41%20AM.png)\n\n2. Clicking Create Signal Route will require you to select/insert the following information:\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/65391416de9cb4e355280743_Screenshot%202023-10-25%20at%209.05.56%20AM.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/65391416de9cb4e355280743_Screenshot%202023-10-25%20at%209.05.56%20AM.png)\n\n* **Route Name:** A friendly name for the signal route.\n* **Sync frequency**: The default frequency for syncing the latest user info to a destination.\n* **Update Rule:** The default operation for syncing the latest user info to a destination. Update only changes existing data, Insert only inserts new data, and Insert or update is a hybrid action that adds new data if it's not already present or updates it if it is.\n* **Source:** The table that holds the latest user info. Usually, it's organized within a User table.\n* **Match Field**: The column used to match and identify users from your source table in the destination system.\n* **Unique Field:** The column that contains values that are distinct for each user in the table.\n* **Connection:** The destination you will sync data to. Please select Klaviyo.\n* **Object Type:** The object that you want to send data to. Please select Identity.\n* **Unique Field:** The column used to match and identify users from the destination system in your source table.\n\n3. Once you finish selecting/inserting the required fields, click Save Route**.**\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/6539142f05b6729e1290271e_Screenshot%202023-10-25%20at%209.06.12%20AM.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/6539142f05b6729e1290271e_Screenshot%202023-10-25%20at%209.06.12%20AM.png)\n\n4. It's time to add the field mappings to activate your signal route. For Klaviyo integration, it's essential to map either Email or Phone, at the very least.\n \n5. To map the field, select the column that represents the Email from the drop-down under Source.\n \n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/6539144ddb281b4514a57e48_Screenshot%202023-10-25%20at%209.06.28%20AM.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/6539144ddb281b4514a57e48_Screenshot%202023-10-25%20at%209.06.28%20AM.png)\n\n‍\n\n6. Under the Destination section, select Email from the drop-down.\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/65391461321acd2ed6a51175_Screenshot%202023-10-25%20at%209.06.41%20AM.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/65391461321acd2ed6a51175_Screenshot%202023-10-25%20at%209.06.41%20AM.png)\n\n7. If you want to map more fields like Phone Number and City, simply click on Add Mapping. This will create a new row for Source > Destination, and then you can follow steps 5 and 6 again.\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/6539147705ef6e4da511c11e_Screenshot%202023-10-25%20at%209.06.52%20AM.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/6539147705ef6e4da511c11e_Screenshot%202023-10-25%20at%209.06.52%20AM.png)\n\n8. Finally, click the toggle at the top of the page to enable the sync!\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/6539148a959a7238510ecfdd_Screenshot%202023-10-25%20at%209.07.06%20AM.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/6539148a959a7238510ecfdd_Screenshot%202023-10-25%20at%209.07.06%20AM.png)\n\n9. Congratulations - you have successfully created a signal sync to Klaviyo!\n\n![https://assets-global.website-files.com/6452937893cd845b6181c39e/6539149f96c744708c85dc19_Screenshot%202023-10-25%20at%209.07.20%20AM.png](https://assets-global.website-files.com/6452937893cd845b6181c39e/6539149f96c744708c85dc19_Screenshot%202023-10-25%20at%209.07.20%20AM.png)\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:35.111Z","6ce917f8-849c-45f0-80be-0dc49d68922d",[],[],{"_40":1446,"_128":1447,"_130":1448,"_132":1449,"_134":-5,"_13":-5,"_120":1450,"_122":136,"_25":1451,"_138":-5,"_139":1452,"_141":1453},"Set up audience approval in GrowthLoop | GrowthLoop Docs","set-up-audience-approval-in-growthloop-growthloop-docs","https://docs.growthloop.com/docs/audience-approval","# Set up audience approval in GrowthLoop\n\nAudience Approval makes it easy to review and approve audiences before they go live. Learn how to set it up for your org!\n\nGrowthLoop makes it easy to size audiences for marketing campaigns, but sometimes a second look is needed before launch. You might want to double-check that the right people are included, confirm the audience actually fits your campaign goals, or others. With **Audience Approval**, reviewing audiences is simple and ensures everything is set up for success.\n\nBelow, we’ll walk through how to:\n\n1. **Enable Audience Approval** in your GrowthLoop account.\n2. **Submit an audience for approval** before exporting.\n3. **Review and approve audiences** as an admin.\n\n> 📘\n> \n> This section applies only to **Admins** and **Owners**.\n\n1. In the left-hand navigation bar, go to **Organization** > **Teams**.\n2. Select the **Team** for which you want to enable **Audience Approval**.\n3. Scroll down to find the **Require admin approval for new audiences** checkbox.\n4. **Check** the box and click Save. Now, all users in that team must go through the Audience Approval process before exporting an audience.\n\n> 📘\n> \n> Only **Owners** and **Admins** can review and approve audiences (including their own). **Users** can only submit audiences for approval.\n\n1. After creating and saving an audience, click **Submit for Approval**.\n2. The audience status will change from **Draft** to **Pending Approval** (visible in the top-left corner).\n3. **Admins** and **Owners** subscribed to the **Audience Ready for Review** notification will receive an alert. Learn how to configure [Email Alerts](https://docs.growthloop.com/docs/email-alerts).\n4. Once approved, the audience status will update to **Approved**, allowing it to be exported to a destination.\n\n> 📘\n> \n> This section applies only to **Admins** and **Owners** who have permission to approve audiences.\n\n1. Navigate to the **Review** page in the left-hand navigation bar.\n2. Select an audience from the list to review.\n3. Review the audience criteria. If everything looks good, click **Approve**. Once approved, the audience can be exported and activated.\n\nWith **Audience Approval**, you can ensure that every audience meets your campaign goals before activation. This process helps maintain accuracy, improves targeting, and adds an extra layer of oversight.\n\n> 📘\n> \n> Experiencing any issues with **Audience Approval**? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and we’ll be in touch shortly to help resolve the matter!\n\nUpdated 5 months ago\n\n* * *","2025-06-20T22:58:32.658Z","b2a7994c-c30c-4b9f-b11b-fb5f618301a6",[],[],{"_40":1455,"_128":1456,"_130":1457,"_132":1458,"_134":-5,"_13":-5,"_120":1459,"_122":136,"_25":1460,"_138":-5,"_139":1461,"_141":1462},"Set up computed fields | GrowthLoop Docs","set-up-computed-fields-growthloop-docs","https://docs.growthloop.com/docs/attributes","In this article, you'll learn how to create Custom Fields to leverage in syncs, audiences and journeys.\n\nAs you are building audiences and journeys in GrowthLoop, you may notice that you would like to apply filters on a customer attribute such as \"Total Purchase Count\" that doesn't exist on any table in your data cloud. GrowthLoop enables you to easily create and add these fields to your Audience and Journey Builder with **Computed Fields**.\n\nGrowthLoop Computed Fields empower your teams to add new calculated fields to your Audience and Journey Builder to create more sophisticated targeting. Use this feature to:\n\n* `Count` — Create a field that counts occurrences of a given action for customers. For example, counting the number of login events in the past 30 days for each user.\n* `Aggregate` — Create a field that calculates Sum, Average or Median values. For example, aggregate the total value of purchases in the past 14 days by user.\n* `Occurrence` — Create a field that shows a value from an action occurring **First**, **Last**, **Most Frequent** or **Least Frequent”**. For example, create a field that shows the name of the last purchased product for each user.\n* `List` — Create an array or comma-separated list of values OR a list of **objects** if multiple table fields are selected”.\n * For example, create a field that lists all product categories purchased by a user.\n * Or, create a field that contains the last 3 posts by a user with all their metadata.\n\nThese Computed Fields are stored as views in your data cloud and are able to be used in your Audience or Journey building by users.\n\n \n\n1. Navigate to the **Models** tab on the left side of the GrowthLoop app.\n\n![](https://files.readme.io/c170d4d-models_navigation.png)\n\n‍\n\n2. Click **Create Model**.\n3. Provide a name for your model and decide whether you want the model **Enabled or Disabled.**\n 1. **Enabled:** Your model will become immediately available as a dataset for audience segmentation.\n 2. **Disabled:** Your model will be kept in “draft mode” and will not be available as a dataset. You can come back and **Enable** the model at another time.\n4. Select **Model Type** as **User Trait**\n5. Select **Dataset Group**: This is the dataset group you would like to add your new computed field to.\n6. Select **Join Key**: The join key simply specifies how you would like us to connect your new computed field to your primary dataset in the dataset group. Typically this is the unique key for your primary dataset. For example, `customer id` or `user id`.\n\nThere are two ways to create a computed field.\n\n1. **Marve Computed Fields**: You can use Marve and simply describe the field you'd like to create, and we'll write the SQL for you and show the results. Note: This feature is currently in **Private Preview**.\n2. **SQL Computed Fields**: You can write SQL to create your computed field. This allows you to create highly custom computed fields to use as filters in your builders.\n\n \n\n1. Describe the field you'd like to create and add to your primary dataset. In this example, we'll use the prompt `total transaction count` to create a field that aggregates a count all transactions done by a user.\n\n![](https://files.readme.io/f5e4d9f-marve_computed_prompt2.png)\n\n2. Click **Generate**\n3. View **Preview** of new field. You can see the results of your new field appear below your prompt. Take a look and see if it fits your expectations. If it doesn't look quite right, don't worry. You can simply try another description of your field and click **Generate**.\n\n![](https://files.readme.io/9dfe033-Marve_computed_results.png)\n\n4. You have full audit visibility of how the field was created in the **SQL** section. If you are technical, you can check the query to ensure it is using the underlying tables you expect for this computed field.\n\n![](https://files.readme.io/7747511-marve_sql_audit.png)\n\n5. Next you have to set up the fields **data type** as well as connect it to the primary table (eg, your customer's table).\n \n In the example below, you can see that we are creating a **User Trait** to count the number of purchases each customer has made.\n \n We have inspected the SQL and preview of results and feel good about saving this new user trait.\n \n So we go ahead and\n \n * have the new column name be under **purchase\\_occurrence\\_count**\n * its data type be **integer**\n * join the computed field to the primary dataset using **customer\\_id**, the unique identifier specified in the computed field for data matching\n \n ![](https://files.readme.io/36b00643df685662e1efda46df04da0124bd2f608819812ff414f8bcd139c507-image.png)\n \n \n \n6. Click **Save**\n \n\nCongratulations, you have created your first **Computed Field**. You can now create audiences, syncs, and journeys using this field and leverage it as a personalization attribute you send to destinations!\n\nExample **Computed Field** in Audience Builder:\n\n![](https://files.readme.io/9890351-marve_computed_builder.png)\n\nExample **Computed Field** in Audience Export as personalization field.\n\n![](https://files.readme.io/86b36dd-compute_field_personalization.png)\n\nThe second option for creating computed fields is to use SQL. There are a couple key concepts to know before you start writing SQL.\n\n* **Input:** You are able to write SQL only on datasets and tables your **Source Connection** is provisioned access to. This typically includes any tables in your dataset group.\n* **Output** Your SQL must contain two columns as the output of your Select statement.\n * **Join Key** : This is the field that connects your computed field to your primary dataset table. This must match the name of the **Join Key** you selected in the dropdown menu on your computed field. We will join your computed field to your primary dataset table on this field.\n * **Computed Field**: This is your computed field that you will be calculating in the rest of the query.\n\nNow that you know the format for computed fields, we'll run through an example together.\n\n1. Write SQL for **Computed Field**\n \n2. **Write Select Statement**\n \n 1. Include your Join Key: Ensure this has the same name as your join key selected above.\n 2. Include your computed field.\n\n![](https://files.readme.io/f27afba-join_key.png)\n\n3. **Write your Computed Field.** In this case we are:\n 1. **WHERE Clause:** Filtering a transactions table to the transactions that have occured in the past 30 days\n 2. **GROUP BY:** Grouping by customer id so we are \"counting\" the transactions per user\n\n![](https://files.readme.io/54b9825-computed_field_sql.png)\n\n4. Click **Preview** to view 20 results.\n\n![](https://files.readme.io/58691af-computed_field_preview.png)\n\n5. Click **Save Model**\n\nHere are some examples queries and results to better show you how computed fields can be used. For all the examples below, these are the tables that we have with their respective relationships.\n\n1. Users table -- basic user info such as customer\\_id, first\\_name and last\\_name\n2. Transactions table -- transaction details such as transaction date, value and item\n3. Blog activity table -- whether the user published a blog post or commented on one\n\nTables 2 & 3 are joined to Table 1\n\n**Now let's get to our examples**\n\n1. **Total number of purchases per customer**\n \n ```\n SELECT\n c.customer_id,\n COUNT(cf.id) as total_purchases\n FROM\n `rokham.customers` c\n LEFT JOIN `rokham.computed-field-transactions` cf ON c.customer_id = cf.customer_id\n GROUP BY\n c.customer_id\n ```\n \n ![](https://files.readme.io/6f2c709-image.png)\n \n2. **Last purchased item**\n \n ```\n SELECT \n c.customer_id,\n ARRAY_AGG(\n purchased_item\n ORDER BY\n transaction_date DESC\n LIMIT\n 1\n ) [OFFSET(0)] as last_purchased_item\n FROM\n `rokham.customers` c\n LEFT JOIN `rokham.computed-field-transactions` t ON c.customer_id = t.customer_id\n GROUP BY\n c.customer_id\n ```\n \n \n \n3. **List of purchased items by each customer**\n \n ```\n SELECT \n c.customer_id,\n ARRAY_AGG(COALESCE(ctf.purchased_item, 'No Purchase')) AS purchased_items_list\n FROM\n `rokham.customers` c\n LEFT JOIN `rokham.computed-field-transactions` ctf ON c.customer_id = ctf.customer_id\n GROUP BY\n c.customer_id\n ```\n \n ![](https://files.readme.io/1c3b3ef-image.png)\n \n\n \n\n4. **Users who have ONLY published a blog post and no comments**\n \n Please note that the preview screenshot below, only shows those who are **not** just authors as a sample set of results.\n \n ```\n SELECT \n c.customer_id,\n IF(\n cfba2.blog_publish_date IS NOT NULL\n AND cfba2.comment_publish_date IS NULL,\n TRUE,\n FALSE\n ) AS author_only\n FROM\n `rokham.customers` c\n LEFT JOIN `rokham.computed-field-blog-activity-2` cfba2 ON c.customer_id = cfba2.customer_id\n ```\n \n ![](https://files.readme.io/dcb12a4-image.png)\n \n\nCongratulations, you have created a **Computed Field** using SQL. You can now create audiences, syncs, and journeys using this field and leverage it as a personalization attribute you send to destinations\n\nUpdated 5 months ago\n\n* * *\n\n* [Set Up Models](https://docs.growthloop.com/docs/models)","2025-06-20T22:58:29.931Z","9e6fbcd8-afa1-433e-936c-7da1267467cd",[],[],{"_40":1464,"_128":1465,"_130":1466,"_132":1467,"_134":-5,"_13":-5,"_120":1468,"_122":136,"_25":1469,"_138":-5,"_139":1470,"_141":1471},"Set up Constant Contact as a destination | GrowthLoop Docs","set-up-constant-contact-as-a-destination-growthloop-docs","https://docs.growthloop.com/docs/constant-contact","# Set up Constant Contact as a destination\n\nThis article outlines the steps necessary to set up Constant Contact as a GrowthLoop destination. Once connected, you can begin sending audience segments to Constant Contact for activation!\n\n* Constant Contact account\n\nSelect **Destinations** from the left rail of your GrowthLoop home screen.\n\n![](https://files.readme.io/3ae8339-Untitled_3.png)\n\nClick **New** **Destination** on the top right.\n\n![](https://files.readme.io/0eb0597-mailchimp_new_destination.png)\n\nScroll to the **Email** section and click **Add Constant Contact**.\n\n![](https://files.readme.io/401c341-select_constant_contact.png)\n\nIf your browser is not already logged into your Constant Contact account, you will be prompted to log in.\n\n![](https://files.readme.io/ca71919-constant_contact_login.png)\n\nYou will be redirected back to GrowthLoop, where you will fill out your **Destination** information.\n\n![](https://files.readme.io/5344ebb-constant_contact_destination_configuration.png)\n\n* **Destination Name:** A custom name for your destination.\n* **Sync Frequency:** The frequency at which GrowthLoop will export audiences to your destination (hourly or daily).\n* **Refresh Token**: A security credential that will auto-populate.\n\nTo export an audience to your Constant Contact destination, navigate to the **Audiences** page and click on your desired audience.\n\n![](https://files.readme.io/c5145e6-audience_list.png)\n\nClick **Export** on the top left.\n\n![](https://files.readme.io/ac033ab-audience_export.png)\n\nSelect your Constant Contact destination and add any fields you want to export with your audience. Click **Start Export.**\n\n![](https://files.readme.io/b914640-constant_contact_personalization.png)\n\nTo see your audience in Constant Contact, navigate to the **Contacts** tab and search for your audience name.\n\n![](https://files.readme.io/15417b4-constant_contact_list.png)\n\nYou’re all set to activate customers to Constant Contact - happy exporting!\n\nExperiencing any issues connecting to Constant Contact as a destination? Reach out to us at **[support@growthloop.com](mailto:support@growthloop.com)** and we’ll be in touch shortly!\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:26.359Z","d04d1426-7ff8-449b-80cc-88cd1e5c63e7",[],[],{"_40":1473,"_128":1474,"_130":1475,"_132":1476,"_134":-5,"_13":-5,"_120":1477,"_122":136,"_25":1478,"_138":-5,"_139":1479,"_141":1480},"Set up GrowthLoop Single Sign On (SSO) | GrowthLoop Docs","set-up-growthloop-single-sign-on-sso-growthloop-docs","https://docs.growthloop.com/docs/single-sign-on-sso","# Set up GrowthLoop Single Sign On (SSO)\n\nLearn how to setup Single Sign On\n\nIn this article, we'll cover GrowthLoop's support for Single Sign-On (SSO) and the various identity providers and protocols that you can use for your SSO configuration. GrowthLoop supports SSO to provide a seamless and secure authentication experience. You can configure SSO with GrowthLoop using your identity provider and connect via **SAML (Security Assertion Markup Language)**, **OIDC (OpenID Connect)** protocols, or **LDAP** protocols.\n\nWhile we support multiple protocols, most of our SSO integrations are done via **SAML**, and this guide will assume a SAML configuration for your setup.\n\nGrowthLoop (via Auth0) currently supports the following identity providers and services with streamlined integrations:\n\n* [ADFS](https://auth0.com/docs/authenticate/identity-providers/enterprise-identity-providers/adfs)\n* [Azure Active Directory Native](https://auth0.com/docs/authenticate/identity-providers/enterprise-identity-providers/azure-active-directory-native)\n* [Okta](https://auth0.com/docs/authenticate/identity-providers/enterprise-identity-providers/okta)\n* [Active Directory/LDAP](https://auth0.com/docs/authenticate/identity-providers/enterprise-identity-providers/active-directory-ldap)\n* [Google Workspace](https://auth0.com/docs/authenticate/identity-providers/enterprise-identity-providers/google-apps)\n* [PingFederate](https://auth0.com/docs/authenticate/identity-providers/enterprise-identity-providers/ping-federate)\n* [Azure Active Directory](https://auth0.com/docs/authenticate/identity-providers/enterprise-identity-providers/azure-active-directory/v2)\n* Custom connections to any [SAML](https://auth0.com/docs/authenticate/identity-providers/enterprise-identity-providers/saml) or [OIDC-compatible](https://auth0.com/docs/authenticate/identity-providers/enterprise-identity-providers/oidc) identity provider\n\nFollow these steps to configure Single Sign-On (SSO) with an Identity Provider in GrowthLoop, assuming a SAML setup. Need help? Your Solutions Architect will be available to support you throughout the process!\n\nIf your organization uses a multi-tenant environment, GrowthLoop will set up a custom URL for your dedicated SSO login. This requires coordination with our engineering team to update the domain and deploy the new environment. The domain format will be `{client}.flywheelproducts.com`.\n\n> 📘\n> \n> This step is unnecessary if your organization uses a single-tenant environment.\n\nTo set up an SSO connection in your identity provider (e.g., Okta, Azure AD), you'll need the following information from your Solutions Architect:\n\n* **Client ID**: `urn:auth0:vortex-prod:{-connection}`\n* **Reply URL (Assertion Consumer Service URL)**: `https://vortex-prod.auth0.com/login/callback?connection={-connection}`\n* **Sign-On URL (Sign-in Redirect URIs)**: `https://vortex-prod.auth0.com/login/callback?connection=-connection`\n* **Logout URL**: `https://.flywheelproducts.com/auth/logout`\n* **Trusted Origins**: `https://app.flywheelproducts.com`\n\nIn response, provide your Solutions Architect with the following information from your side:\n\n* **Sign-In URL**\n* **X509 Signing Certificate**\n* **Data mappings for user\\_id and email**\n\nOnce your domain is set up, your Solutions Architect will configure the SAML connection in Auth0. The connection name in Auth0 must match `{client}-connection` to dynamically update your login page with your organization's SSO configuration.\n\n* **Sign-In URL**: Provided by your identity provider during the setup process.\n* **X509 Signing Certificate**: Obtained during your setup process with your identity provider.\n* **Data Mappings**: Ensure correct mappings for `user_id` and `email`. These values will determine how users are identified and routed within our system.\n\nWe recommend conducting a thorough testing phase to ensure that the connection is working as expected. This can often be done by GrowthLoop without involving you directly, especially if your Solutions Architect has access to your system. However, if needed, we can coordinate a call to assist with debugging.\n\n1. **Enable Debug Mode**: Set the connection to debug mode in the Auth0 connection settings.\n2. **Monitor Logs**: Use Auth0's \"Monitoring\" > \"Logs\" section to track login attempts.\n3. **Test Login**: Have someone from your organization attempt a login. Review the logs to ensure proper authentication and data mappings.\n4. **Final Configuration:** Adjust any mappings as needed based on test results. Ensure that user IDs and email attributes are correctly configured.\n\nIf everything is functioning as expected, the connection will be live, and you will be able to log in using SSO.\n\n> 📘\n> \n> If you experience any issues or have questions during the setup process, please reach out to us at [support@growthloop.com](mailto:support@growthloop.com), and we’ll be in touch shortly!\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:31.210Z","5b0251d5-69a1-4c96-afc7-3b3e44e6bdcf",[],[],{"_40":1482,"_128":1483,"_130":1484,"_132":1485,"_134":-5,"_13":-5,"_120":1486,"_122":136,"_25":1487,"_138":-5,"_139":1488,"_141":1489},"Set up MessageGears as a destination | GrowthLoop Docs","set-up-messagegears-as-a-destination-growthloop-docs","https://docs.growthloop.com/docs/message-gears","# Set up MessageGears as a destination\n\nLearn hwo to add Message Gears as a destination for exports\n\nMessageGears supports picking up audiences that are exported to a data warehouse. To export audiences to MessageGears, you will need to connect a data warehouse as a destination in the GrowthLoop application. When exporting audiences to MessageGears, ensure that your data is in a format that MessageGears will accept.\n\nPlease see our tutorials on connecting to [BigQuery](https://docs.growthloop.com/docs/bigquery) or [Snowflake](https://docs.growthloop.com/docs/snowflake) as destinations, depending on which data warehouse you want to export your audiences to. The requirements provided there apply to setting up an export to MessageGears as well.\n\n![](https://files.readme.io/42591cf-select_message_gears.png)\n\nMessageGears will then pick up audiences the data warehouse.\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:28.448Z","be44f099-6753-40cb-ad00-4bec1967ff7b",[],[],{"_40":1491,"_128":1492,"_130":1493,"_132":1494,"_134":-5,"_13":-5,"_120":1495,"_122":136,"_25":1496,"_138":-5,"_139":1497,"_141":1498},"Set up Microsoft Dynamics as a destination | GrowthLoop Docs","set-up-microsoft-dynamics-as-a-destination-growthloop-docs","https://docs.growthloop.com/docs/microsoft-dynamics","# Set up Microsoft Dynamics as a destination\n\nAdd Microsoft Dynamics as a Destination\n\n1. Navigate to the **Destinations** tab on the left in GrowthLoop.\n2. Click **New Destination**\n\n![](https://files.readme.io/0eb0597-mailchimp_new_destination.png)\n\n3. Search for or navigate to Microsoft Dynamics\n\n![](https://files.readme.io/2dd57e8-select_dynamics.png)\n\n4. Add a Destination Name (We recommend you choose something descriptive like \"Dynamics Production Audiences\") \n Select a Sync Frequency. We'll come back to Instance URL.\n\n![](https://files.readme.io/ba435e1-dynamics_configuration.png)\n\n5. Login to Microsoft Dynamics: dynamics.microsoft.com\n6. Copy your Instance URL. You can find your instance URL in your browser and would be something like this: https://\\[organization\\].crm.dynamics.com/\n\n![](https://files.readme.io/a263c42-dynamics_instance_url.png)\n\n7. Add your Instance URL to GrowthLoop and select \"Create\".\n\n‍\n\n8. Your Microsoft Dynamics account will now be authenticated and will appear on your destinations page and can start configuring audiences to export to Dynamics! \n ‍\n\nExperiencing any issues connecting to Microsoft Dynamics as a destination? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and we’ll be in touch shortly!\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:28.711Z","20bea106-f42b-40b6-957b-41c9d482df59",[],[],{"_40":1500,"_128":1501,"_130":1502,"_132":1503,"_134":-5,"_13":-5,"_120":1504,"_122":136,"_25":1505,"_138":-5,"_139":1506,"_141":1507},"Set up Salesforce CRM as a destination | GrowthLoop Docs","set-up-salesforce-crm-as-a-destination-growthloop-docs","https://docs.growthloop.com/docs/salesforce-crm","# Set up Salesforce CRM as a destination\n\nSetup Salesforce CRM as a destination to send exports\n\nSalesforce is a leading cloud-based software for customer relationship management (CRM), empowering companies to better connect with leads and established customers alike. GrowthLoop amplifies the power of CRM by allowing you to segment these individuals across any metric in your data warehouse, paving the way for more relevant and targeted campaigns. This article outlines the steps necessary to set up Salesforce as a GrowthLoop destination and begin exporting audiences for activation.\n\nBefore connecting Salesforce to the application, we will walk through one requirement:\n\n* Creating a Security Token\n\nConnecting Salesforce as an audience destination requires a **security token** specific to your Salesforce account. If you do not know your security token, you will need to reset it using the steps below\\_.\\_ If you know your token, skip to **Connecting Salesforce as a Destination**.\n\nLog in to Salesforce with your username and password. From the home screen, click your **User Icon** at the top right corner and select **Settings**.\n\n![](https://files.readme.io/4bcb8be-salesforce_profile_settings.png)\n\nType “token” into the **Quick** **Find** bar in the left rail and click **Reset My Security Token.**\n\n![](https://files.readme.io/dc30ddf-salesforce_security_token.png)\n\nClick **Reset Security Token.** A new token will be sent to the email address associated with your Salesforce account.\n\n![](https://files.readme.io/7c60cea-salesforce_security_token_confirm.png)\n\nOnce you know your security token, you’re ready to connect Salesforce as an audience destination!\n\nSelect **Destinations** from the left rail of your GrowthLoop home screen.\n\nClick **New** **Destination** on the top right.\n\n![](https://files.readme.io/0eb0597-mailchimp_new_destination.png)\n\nScroll down to the **CRM** section of the pop-up window and click **Add Salesforce Audience**.\n\n![](https://files.readme.io/96964c8-select_salesforce_crm.png)\n\nComplete all **Destination Info** and **Credentials** fields (see below for assistance), then click **Create.**\n\n![](https://files.readme.io/df43c97-configure_salesforce_crm.png)\n\n* **Destination Name:** A custom name for your destination.\n* **Sync Frequency:** The frequency at which GrowthLoop will export audiences to your destination (hourly or daily).\n* **Username:** Your Salesforce username.\n* **Password:** Your Salesforce password.\n* **Security Token:** Your Salesforce security token.\n* **Dev Environment:** Check this box if your Salesforce destination is a sandbox (development) environment. If you aren’t sure, take a look at the Salesforce URL that you use to log in. If this URL begins with “test,” i.e. test.salesforce.com, check the box. If not, leave it empty.\n\nOnce you’ve set up Salesforce as a destination and created an audience, you can begin exporting!\n\n1. Open the target audience and click **Export.**\n\n![](https://files.readme.io/ac033ab-audience_export.png)\n\n2. Find your Salesforce destination and click **Activate.**\n\n![](https://files.readme.io/63813ff-salesforce_activate.png)\n\n3. In the modal window, specify how GrowthLoop should match audience members to your Salesforce leads, contacts and accounts. Each match condition unlocks a different set of actions you can apply to matching and non-matching profiles in Salesforce.\n\n![](https://files.readme.io/208548b-salesforce_match_object.png)\n\n* **Match on Contacts and Leads:** Look for matches across all contacts and leads in Salesforce.\n* **Match on Account:** Look for matches with accounts in Salesforce.\n* **Match on Leads Only:** Look for matches only with Salesforce leads, ignoring contacts.\n* **Create Campaign in Salesforce for each GrowthLoop Audience:** Selecting **Yes** will create a campaign for this audience in your Salesforce instance. To do so, you must have **Marketing User Privileges** assigned to your Salesforce username.\n\nWhen matching on contacts and leads, you have an extensive set of options for customizing your audience export to Salesforce.\n\n**Matching Contacts**\n\nYou can filter all contact matches across opportunity type, owner, and stage, applying a specific action to only contacts who meet these criteria. Available actions include adding tasks, opportunities, and activities. You have the option of assigning this action to either the opportunity owner (by checking **Copy opportunity owner for this task**) or specifying a different owner’s email address.\n\nYou can also choose a separate action to apply to matching contacts who _do not_ meet your opportunity criteria.\n\n![](https://files.readme.io/d6f53f5-salesforce_contact_match.png)\n\n**Matching Leads**\n\nAs with contacts, there are a variety of actions available for matching leads, ranging from updating the lead to converting it to an account and contact.\n\n![](https://files.readme.io/b1922ef-salesforce_matching_leads.png)\n\n**Non-Matching Contacts or Leads**\n\nFinally, you can also take action on any audience member who _does not_ match an existing contact or lead in Salesforce. You can create a new lead or contact (among others) by identifying the fields in your data corresponding to an individual’s company, name, and contact information.\n\n![](https://files.readme.io/3997cea-salesforce_non_matches.png)\n\n**Choosing Match Fields**\n\nFinally, choose the data identifier that will match your GrowthLoop audience members to your Salesforce leads and contacts. This is typically a Contact ID or email address.\n\n![](https://files.readme.io/dad355c-salesforce_match_fields.png)\n\nSelecting “Match on Account” allows you to match on Salesforce account, rather than contact or lead. As with contacts and leads, you can apply actions to accounts right from GrowthLoop!\n\n**Matching Accounts**\n\nYou can filter all account matches across opportunity type, owner, and stage, applying a specific action to only accounts that meet these criteria. Available actions include adding tasks, opportunities, and activities. You have the option of assigning this action to either the opportunity owner (by checking **Copy opportunity owner for this task**) or specifying a different owner’s email address.\n\nYou can also choose a separate action to apply to any contacts who _do not_ match your criteria.\n\n> 📘\n> \n> **Note**\n> \n> When configuring **For Accounts with existing Opportunities** matching these criteria, leaving the criteria fields blank means match any existing opportunity.\n> \n> * If both **For Accounts with existing Opportunities** and **For Accounts without Opportunities** are set to **Create Opportunity**, GrowthLoop will create a new Opportunity for every matched account, even if that account already has one or more Opportunities.\n> * To limit creation only when certain conditions are met, add specific filters in the criteria fields.\n\nSelecting “Match on Leads Only” allows you to match audience members to Salesforce leads only, ignoring Salesforce contacts.\n\n**Matching Leads**\n\nFor matching leads, you can add a task, convert the lead and create an opportunity, or do nothing.\n\n![](https://files.readme.io/88cfbad-salesforce_matching_leads_only.png)\n\n**Non-Matching Leads**\n\nFor audience members that do not match an existing lead, you can create new Salesforce leads or contacts by specifying the fields in your data that correspond with members’ companies, names and contact information.\n\n![](https://files.readme.io/31a5026-salesforce_non_matching_leads_only.png)\n\nExperiencing any issues connecting to Salesforce as a destination? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and we’ll be in touch shortly!\n\nUpdated 29 days ago\n\n* * *","2024-03-20T21:02:29.443Z","a9f08318-f51e-492f-a287-aaa51f41ac57",[],[],{"_40":1509,"_128":1510,"_130":1511,"_132":1512,"_134":-5,"_13":-5,"_120":1513,"_122":136,"_25":1514,"_138":-5,"_139":1515,"_141":1516},"Set up Salesforce Pardot as a destination | GrowthLoop Docs","set-up-salesforce-pardot-as-a-destination-growthloop-docs","https://docs.growthloop.com/docs/salesforce-pardot","# Set up Salesforce Pardot as a destination\n\nLearn how to set Pardot as a destination for audience exports.\n\nPardot is a marketing automation add-on to Salesforce’s cloud-based software for customer relationship management (CRM). This article outlines the steps necessary to set up Pardot as a GrowthLoop destination and begin exporting audiences for activation.\n\n* Pardot username and password\n* Salesforce business account ID\n* Salesforce security token\n\nIf you already have these credentials on hand, you can skip down to **Setting Pardot as a Destination.** If not, see below for instructions on finding your business account ID and security token.\n\nLog into Salesforce using the same account you use to log into Pardot. From the home screen, type **Pardot** into the **Quick Find** bar.\n\n![](https://files.readme.io/05cdf8a-salesforce_navigation.png)\n\nClick **Pardot Account Setup** and find your **Business Unit ID** from the list that appears. Make sure to select your own business unit. This is the ID you will use for GrowthLoop destination setup.\n\n![](https://files.readme.io/0c3d42a-salesforce_pardot_settings.png)\n\nIf you do not know your Salesforce security token, you will need to reset it.\n\nLog in to Salesforce with your username and password. From the home screen, click your **User Icon** at the top right corner and select **Settings**.\n\n![](https://files.readme.io/da933dd-pardot_profile_settings.png)\n\nType “token” into the **Quick** **Find** bar in the left rail and click **Reset My Security Token.**\n\n![](https://files.readme.io/b7b971c-pardot_reset_security_token.png)\n\nClick **Reset Security Token.** A new token will be sent to the email address associated with your Salesforce account.\n\n![](https://files.readme.io/09b22ad-pardot_reset_security_token_confirmation.png)\n\nOnce you know your business account ID and security token, you’re ready to connect Pardot as an audience destination!\n\nSelect **Destinations** from the left rail of your GrowthLoop home screen.\n\nClick **New** **Destination** on the top right.\n\n![](https://files.readme.io/0eb0597-mailchimp_new_destination.png)\n\nScroll down to the **Email** section and click **Add Pardot**.\n\n![](https://files.readme.io/4794881-select_pardot_destination.png)\n\nA modal window will prompt you to fill out **Destination Info** and **Credentials**.\n\n![](https://files.readme.io/fc0fa00-pardot_destination_configuration.png)\n\n* **Destination Name:** A custom name for your destination.\n* **Sync Frequency:** The frequency at which GrowthLoop will export audiences to your destination (hourly or daily)\n* **Username:** Your Salesforce username\n* **Password:** Your Salesforce password\n* **Security Token:** Your Salesforce security token\n* **Business Account ID:** Your business unit ID\n\nClick **Create** and you are set to export your first audience to Salesforce Pardot! You can confirm that your Pardot account is connected by clicking **Destinations** on the left rail.\n\n![](https://files.readme.io/d88d983-pardot_destination_list.png)\n\nHappy exporting!\n\nExperiencing any issues connecting to Pardot as a destination? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and we’ll be in touch shortly!\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:29.800Z","5d459b27-542f-4476-9d28-fd6bdcf8955d",[],[],{"_40":1518,"_128":1519,"_130":1520,"_132":1521,"_134":-5,"_13":-5,"_120":1522,"_122":136,"_25":1523,"_138":-5,"_139":1524,"_141":1525},"Set up the GrowthLoop Personalization API | GrowthLoop Docs","set-up-the-growthloop-personalization-api-growthloop-docs","https://docs.growthloop.com/docs/personalization-api","# Set up the GrowthLoop Personalization API\n\nThe Personalization API lets you personalize web and mobile application experiences. It is a lightning-fast way to get customer information from a performant API on your cloud data stack. You can see customer information to use in personalization and the audiences a user is currently qualified for.\n\nFor instance, let's say you define a churned, high-spender audience called \"Churned High Value\". When a user visits your app, you can check if they are in this audience to decide whether to give them an incentive to purchase to win them back.\n\nAccess is controlled in GrowthLoop's SaaS environment using an API key, please have your designated admin reach out to your assigned solutions architect to receive your API key. When making requests to the personalization API, you’ll need to pass an Authorization header with a value of Bearer base64\\_encoded\\_api\\_key.\n\n```\n\n```\n\nTo list all available segments in your organization, you can use the endpoint listed above. This will return the Audience Name and Audience ID of all audiences currently exported to the personalization API.\n\n**Sample Call:**\n\n```\ncurl --location --request GET 'https://app.flywheelsoftware.com/v1/audiences' --header 'Authorization: Bearer ************************\n```\n\n**Sample Response:**\n\n```\n[ \n { \n \"audience_id\":2100, \n \"audience_name\":\"Churned High Spenders\" \n }, \n { \n \"audience_id\":2101, \n \"audience_name\":\"High Frequency Buyers\" \n } \n]\n```\n\n‍\n\n```\n\n```\n\n‍To list all audiences a user is a part of, you can query the base endpoint listed above and include an identifier parameter. The identifier parameter is tied to the unique identifier mapping chosen when connecting your Users Datasets to GrowthLoop.\n\n‍\n\nIn addition to the audiences a user is a member of, this endpoint also returns customer profile information instantly from any Users Dataset or Users Model configured in Flywheel from your data warehouse. You can query the base endpoint listed above and include an identifier parameter. The identifier parameter is tied to the unique identifier mapping chosen when connecting your Users Dataset to Flywheel. This is great for serving personalization, recommendations, or creatives stored for a customer in your data warehouse.\n\n‍\n\n**Sample Call:**\n\n```\ncurl --location --request GET ' --header 'authorization: Bearer ************\\*\\*\\*\\*************\n```\n\n‍\n\n**Sample Response:**\n\n```\n{ \n \"id\": 1729271, \n \"first_name\": \"Joe\",\n \"last_name\": \"Cristee\",\n \"audiences\": [\n { \n \"audience_id\": 2100, \n \"audience_name\": \"Churned High Spenders\" \n },\n { \n \"audience_id\": 152, \n \"audience_name\": \"Incentive User\" \n }\n ],\n \"total_spend\": 572.00,\n \"churn_risk_score\": 0.78\n \"last_purchase_date\": \"12/21/2020\",\n \"gender\": \"Male\",\n \"most_frequent_purchase_category\": \"Electronics\",\n \"last_purchase_category\": \"Shoes\",\n \"incentive_recommendations\": {\n \t\"incentives\": [\n {\n \"id\": 4\n \"name\": \"Buy $50, Get Free Shipping\"\n \"expiration\": \"12/30/2020\"\n },\n {\n \"id\": 6\n \"name\": \"20% off\"\n \"expiration\": \"12/30/2020\"\n },\n ]\n }\n}\n```\n\nOur customers are leveraging the Personalization API to bring the power of their Cloud Data Stack to drive personalized experiences in mobile applications and their CMS. If you are interested in learning more reach out to [support@growthloop.com](mailto:support@growthloop.com).\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:33.204Z","f3ad30f9-4daa-4895-86ef-ff94f29d4b08",[],[],{"_40":1527,"_128":1528,"_130":1529,"_132":1530,"_134":-5,"_13":-5,"_120":1531,"_122":136,"_25":1532,"_138":-5,"_139":1533,"_141":1534},"Set up TheTradeDesk as a destination | GrowthLoop Docs","set-up-thetradedesk-as-a-destination-growthloop-docs","https://docs.growthloop.com/docs/trade-desk","# Set up TheTradeDesk as a destination\n\nLearn how to connect and send audiences to TheTradeDesk\n\nIn this Help Center article, we will walk you through the steps to get **TheTradeDesk** connected as a destination in the GrowthLoop web application. Once connected, you will be able to send your audience segments to TheTradeDesk for marketing activation!\n\n> 📘\n> \n> If you're looking to connect to **TheTradeDesk CRM** please refer to [this doc](https://docs.growthloop.com/docs/the-trade-desk-crm) for details.\n\n* Make sure you have an account. If not, get in touch with TheTradeDesk [here](https://www.thetradedesk.com/us/contact-us)!\n* Have your **First Party Data Key** and **Advertiser ID** ready. Locate them in the **Advertiser Preferences** section in your TheTradeDesk account.\n\n1. Log into **GrowthLoop** and click the **Destinations** tab on the left sidebar.\n2. Then click **New Destinations** on the upper right side.\n3. Next, search for **TheTradeDesk** in the destination modal and click **Add TheTradeDesk**.\n4. Enter the required information in the modal, then click **Create**.\n 1. **Destination Name:** This is how the destination will be named and referred to in to the app going forward. It is helpful to make this name “marketer friendly” so everyone on your team knows it’s purpose.\n 2. **Sync frequency**: This is the default frequency audiences will be synced to a destination. Marketers can always change the frequency of an export to TheTradeDesk, but this sets the default.\n 3. **First Party Data Key** and **Advertiser ID**: For these 2 parameters, you can navigate to your account on TheTradeDesk and select the Ads Account you want to add as a destination (as per the screenshot below).\n\n![](https://files.readme.io/2fcdd25-Screenshot_2023-07-19_at_8.23.11_AM.png)\n\n5. Navigate to your list of audiences by clicking the **Audiences** tab on the left sidebar.\n6. Choose an existing audience or create a new one. Need help creating? Click [here](https://docs.growthloop.com/docs/create-an-audience) to learn how!\n7. Once created, click the **Export** button on the upper right side.\n8. Search for **TheTradeDesk** in the export modal and then click **Add TheTradeDesk**.\n9. Map at least one user identifier. Here's what is currently supported:\n 1. **UID2**: A 256-bit UID2 represented as a base64-encoded string.\n 2. **Trade Desk ID (TDID)**: A 36-character ID (including dashes) assigned by The Trade Desk for a user.\n 3. **Raw Device ID (DAID)**: The raw device ID for the user, provided in a 36-character GUID format, including dashes. This can be either the iOS IDFA or Android's AAID.\n 4. **RampID**: A 49-character or 70-character RampID, previously known as IdentityLink. This RampID must be specifically mapped for The Trade Desk through LiveRamp. For mapping instructions, refer to LiveRamp [documentation](https://sidecar.readme.io/docs/getting-started).\n 5. **ID5**: Data providers holding these IDs should communicate directly with ID5 to obtain the necessary decryption keys. For more information, visit the ID5 website. NOTE: The ID5 ID must be in decrypted form.\n 6. **IDL**: LiveRamp Identity Link\n 7. **UID2Token**: An encrypted UID2 token.\n\n> 📘\n> \n> Mapping more fields leads to a higher match rate!\n\n10. Configure your export settings:\n 1. **Export Name**: Automatically populated with your audience name for easy identification in the destination.\n 2. **Campaign Type**: Choose between a one-time export or ongoing basis.\n 3. **Export Schedule**: Set the frequency, start date, end date, and specific days of the week.\n11. Lastly, click **Export**. Congrats on successfully exporting an audience to TheTradeDesk! To view your audience, log in to your account, click the **Data** tab, and select **My Imported Data**.\n\n![](https://files.readme.io/3078d25-imported_list_in_TTD.png)\n\n> 📘\n> \n> Experiencing any issues when connecting to The Trade Desk? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and we’ll be in touch shortly to help resolve the matter!\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:30.403Z","1e10541b-193b-46d0-a0c7-88d79857ae2c",[],[],{"_40":1536,"_128":1537,"_130":1538,"_132":1539,"_134":-5,"_13":-5,"_120":1540,"_122":136,"_25":1541,"_138":-5,"_139":1542,"_141":1543},"Set up TheTradeDesk CRM as a destination | GrowthLoop Docs","set-up-thetradedesk-crm-as-a-destination-growthloop-docs","https://docs.growthloop.com/docs/the-trade-desk-crm","# Set up TheTradeDesk CRM as a destination\n\nExport CRM segments from your Data Warehouse to **TheTradeDesk CRM** for precise ad targeting and enhanced campaign performance.\n\nIn this Help Center article, we will walk you through the steps to get **TheTradeDesk CRM** connected as a destination in the GrowthLoop web application. Once connected, you will be able to send your CRM segments to **TheTradeDesk CRM** for data orchestration!\n\nIf you're looking to connect to **The Trade Desk** instead please refer to [this doc](https://docs.growthloop.com/docs/trade-desk) for details.\n\nBefore you begin this process, you must have a **TheTradeDesk CRM** account setup. Click [here](https://www.thetradedesk.com/us/contact-us) to request a demo from a Trade Desk Representative.\n\n1. When you sign into the GrowthLoop Platform, navigate to the **Destinations** tab on the left sidebar and click **New Destination** in the top right corner.\n\n![](https://files.readme.io/8534b2d-Untitled.png)\n\n1. When the **Select Destination** window pops up, type **TheTradeDesk CRM** into the Search Bar to find **TheTradeDesk CRM** and click **Add TheTradeDesk CRM**.\n\n![](https://files.readme.io/2df0ef3-Untitled_1.png)\n\n1. Clicking **Add TheTradeDesk CRM** will require you to select/insert the following information:\n\n![](https://files.readme.io/eadbb2e-Untitled_2.png)\n\n* **Destination Name:** This is how the destination will be named and referred to in to the app going forward. Making this name “marketer friendly” is helpful so everyone on your team knows its purpose.\n* **Sync frequency**: This is the default frequency CRM segments will be synced to a destination. Marketers can always change the frequency of an export to **TheTradeDesk CRM**, but this sets the default.\n* **Account ID:** The ID that uniquely identifies your organization within the **TheTradeDesk** Platform.\n* **API Key:** This key identifies your application when making API requests.\n\n3. Go ahead and select **Create**, and we’ll validate we have all the proper permissions to load data to **TheTradeDesk CRM**. You should now see **TheTradeDesk CRM** in your list of connected destinations!\n\n![](https://files.readme.io/d48426a-TTD_destination_created.png)\n\n1. To build a CRM segment and export it to **TheTradeDesk CRM**, click **New Audience**.\n\n![](https://files.readme.io/b30af21-Screen_Shot_2023-04-30_at_9.21.23_PM.png)\n\n2. In the Builder, create your desired CRM segment. Once you finish building the CRM segment, click **Export**.\n\n![](https://files.readme.io/677c8d0-Untitled_3.png)\n\n3. When the **Create Export** window pops up, type **TheTradeDesk CRM** into the search bar and click **Select**.\n\n![](https://files.readme.io/effb491-Untitled_4.png)\n\n4. By default, the name field will auto-populate to your CRM segment name so you can easily find it in your destination. You can then select your campaign type, export schedule, and sync end date. Click the **Start Export** button.\n\n![](https://files.readme.io/d09a005-Untitled_5.png)\n\n5. You can also click the **Match Field** pill menu and select the fields you want to match against from your data warehouse to TheTradeDesk CRM.\n \n Please note that The Trade Desk CRM supports 2 fields as match fields on their end which are **Email & Phone number.**\n \n6. Once you export a CRM segment to the **TheTradeDesk CRM**, you can log in to your **TheTradeDesk CRM** account and see if it was successfully routed to **TheTradeDesk CRM**. Here, you will find your newly exported CRM segment in the list.\n \n\n![](https://files.readme.io/724cc1c-imported_list_in_TTD.png)\n\nAnd that’s it! You’ve successfully exported a CRM segment to **TheTradeDesk CRM** for data orchestration!\n\nAre you experiencing any issues when connecting to **TheTradeDesk CRM**? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and we’ll be in touch shortly to help resolve the matter!\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:30.770Z","96a15b9e-377f-4472-b2ea-7c79738e9b89",[],[],{"_40":1545,"_128":1546,"_130":1547,"_132":1548,"_134":-5,"_13":-5,"_120":1549,"_122":136,"_25":1550,"_138":-5,"_139":1551,"_141":1552},"Set up your minimum audience requirements | GrowthLoop Docs","set-up-your-minimum-audience-requirements-growthloop-docs","https://docs.growthloop.com/docs/audience-exporting-and-reporting-size-requirements","# Set up your minimum audience requirements\n\n## Audience Exporting and Reporting Size requirements\n\nIn this article, we will walk you through the steps to set a **minimum audience size requirement for** **exporting** and **reporting**. Once configured, you will be able to have greater control over the end users’ ability to view or export small audiences. This feature helps ensure compliance with data privacy guidelines by limiting the user’s ability to reduce an audience down to a pool of small, individually identifiable members.\n\n**Minimum Audience Requirements** directly impact two specific features for the end user: **reporting** on **audience size and exporting** to destinations. The user can configure separate minimum sizes for reporting and exporting. These will prevent the user from either viewing audience size or exporting an audience to a destination when the audience is smaller than the configured threshold.\n\nWhen building an audience that does not meet the minimum report size, an **Audience Too Small** message will be displayed in the reporting panel. The user can hover over the triangular warning sign to view the minimum size requirement currently set for reporting.\n\n![](https://files.readme.io/ad60d22-Untitled.png)\n\nWhen attempting to export an audience that does not meet the minimum export size criteria, the **Export Audience** button will be greyed out and not clickable. When hovering over the export button, the end user will be able to see the required minimum audience size for exports.\n\n![](https://files.readme.io/fe0e835-Untitled_1.png)\n\nThis setting is only available to individuals who have **Admin** and or **Owner** roles in their GrowthLoop organization. After logging onto the platform, navigate to **Datasets** on the left side bar.\n\n![](https://files.readme.io/5b3c8d3-Untitled_2.png)\n\nMinimum Audience size configurations are set on the **Dataset Group** level. That means that you can configure separate thresholds for different dataset groups if you have multiple.\n\n![](https://files.readme.io/c50a4f4-Untitled_3.png)\n\nClick into your desired **Dataset** **Group** and scroll down until you see **Minimum Audience Sizes**. Here you’ll be able to set **Minimum Export Size** and **Minimum Report Size**. By default these values will be set to 0, meaning any audience with any number of qualified members will have reporting and exporting capabilities.\n\n**Congratulations! You’ve unlocked the power to configure minimum audience sizes for both exporting and reporting.**\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:33.490Z","beb30b14-e540-4b14-8ac8-71baa81a1f88",[],[],{"_40":1554,"_128":1555,"_130":1556,"_132":1557,"_134":-5,"_13":-5,"_120":1558,"_122":136,"_25":1559,"_138":-5,"_139":1560,"_141":1561},"show an audience export","show-an-audience-export","https://docs.growthloop.com/reference/get_api-public-exports-id","get https://app.pub.prod.flywheelproducts.com/api/public/exports/\n\n| time | status | user agent | |\n| --- | --- | --- | --- |\n| Make a request to see history. | | | |\n\nClick `Try It!` to start a request and see the response here! Or choose an example:","2024-03-20T21:02:37.357Z","9d854d70-b88a-4bb5-9dde-f85e8498b5c0",[],[],{"_40":1563,"_128":1564,"_130":1565,"_132":1566,"_134":-5,"_13":-5,"_120":1567,"_122":136,"_25":1568,"_138":-5,"_139":1569,"_141":1570},"show audience","show-audience","https://docs.growthloop.com/reference/get_api-public-audiences-id","get https://app.pub.prod.flywheelproducts.com/api/public/audiences/\n\n| time | status | user agent | |\n| --- | --- | --- | --- |\n| Make a request to see history. | | | |\n\nClick `Try It!` to start a request and see the response here! Or choose an example:","2024-03-20T21:02:37.430Z","875eca3d-3a50-4ad4-acb0-6029cc2bfa6c",[],[],{"_40":1572,"_128":1573,"_130":1574,"_132":1575,"_134":-5,"_13":-5,"_120":1576,"_122":136,"_25":1577,"_138":-5,"_139":1578,"_141":1579},"show breakdowns","show-breakdowns","https://docs.growthloop.com/reference/get_api-public-audiences-id-breakdowns-field","get https://app.pub.prod.flywheelproducts.com/api/public/audiences//breakdowns/\n\n| time | status | user agent | |\n| --- | --- | --- | --- |\n| Make a request to see history. | | | |\n\nClick `Try It!` to start a request and see the response here! Or choose an example:","2024-03-20T21:02:37.504Z","e35c631a-0ee6-4d2d-b807-a408ba5e202a",[],[],{"_40":1581,"_128":1582,"_130":1583,"_132":1584,"_134":-5,"_13":-5,"_120":1585,"_122":136,"_25":1586,"_138":-5,"_139":1587,"_141":1588},"show dataset group","show-dataset-group","https://docs.growthloop.com/reference/get_api-public-dataset-groups-id","get https://app.pub.prod.flywheelproducts.com/api/public/dataset\\_groups/\n\n| time | status | user agent | |\n| --- | --- | --- | --- |\n| Make a request to see history. | | | |\n\nClick `Try It!` to start a request and see the response here! Or choose an example:","2025-06-20T22:59:05.712Z","22ac035c-7371-41fc-906b-f6d05319f43b",[],[],{"_40":1590,"_128":1591,"_130":1592,"_132":1593,"_134":-5,"_13":-5,"_120":1594,"_122":136,"_25":1595,"_138":-5,"_139":1596,"_141":1597},"show destination","show-destination","https://docs.growthloop.com/reference/get_api-public-destinations-id","get https://app.pub.prod.flywheelproducts.com/api/public/destinations/\n\n| time | status | user agent | |\n| --- | --- | --- | --- |\n| Make a request to see history. | | | |\n\nClick `Try It!` to start a request and see the response here! Or choose an example:","2024-03-20T21:02:37.747Z","3ce53bb6-376e-4d14-9548-732739653e92",[],[],{"_40":1599,"_128":1600,"_130":1601,"_132":1602,"_134":-5,"_13":-5,"_120":1603,"_122":136,"_25":1604,"_138":-5,"_139":1605,"_141":1606},"show journey","show-journey","https://docs.growthloop.com/reference/get_api-public-journeys-id","get https://app.pub.prod.flywheelproducts.com/api/public/journeys/\n\n| time | status | user agent | |\n| --- | --- | --- | --- |\n| Make a request to see history. | | | |\n\nClick `Try It!` to start a request and see the response here! Or choose an example:","2025-06-20T22:59:06.515Z","09124d06-1af2-46f2-9ec3-3b762855426a",[],[],{"_40":1608,"_128":1609,"_130":1610,"_132":1611,"_134":-5,"_13":-5,"_120":1612,"_122":136,"_25":1613,"_138":-5,"_139":1614,"_141":1615},"show persona brief","show-persona-brief","https://docs.growthloop.com/reference/get_api-public-audiences-id-persona-brief","get https://app.pub.prod.flywheelproducts.com/api/public/audiences//persona\\_brief\n\n| time | status | user agent | |\n| --- | --- | --- | --- |\n| Make a request to see history. | | | |\n\nClick `Try It!` to start a request and see the response here! Or choose an example:","2024-03-20T21:02:37.583Z","e475cc79-0676-48aa-8b66-28fae04b8f84",[],[],{"_40":1617,"_128":1618,"_130":1619,"_132":1620,"_134":-5,"_13":-5,"_120":1621,"_122":136,"_25":1622,"_138":-5,"_139":1623,"_141":1624},"Source Connection Management","source-connection-management","https://docs.growthloop.com/docs/source-connection-management","Learn how to manage source connections for your organization\n\nIn this article, you'll learn how to setup and manage source connections to your data clouds and how to use them in different teams. Source Connections are the connection credentials to your Data Cloud. They can be used to allow different teams to create audiences and journeys on different data cloud sources directly from the GrowthLoop Platform.\n\nThe ability to have different source connections to your data cloud projects gives you immense flexibility to enable your marketer teams to complete their tasks, while providing them with only the data they need access to, while maintaining strict privacy and security patterns.\n\nFor example, companies often have different marketing teams servicing specific products and customer bases. For instance, you may have a team (`team 1`) focused on your \"consumer\" customers, and another team (`team 2`) focused on \"business. In this case you may have information on both consumers and businesses in the same data cloud. However, you don't want to get all members of these teams access to data they do not need. A common setup is to create two source connections as follows:\n\n* `Source Connection 1`: Connect to data cloud `consumer` and ensure the credentials only provide access to consumer customer data.\n* `Source Connection 2`: Connect to data cloud `business` and ensure the credentials only provide access to business customer data.\n* In GrowthLoop, you can then provide `team 1` with only the ability to create audiences and journeys based on `Source Connection 1`.\n* In addition, you can provide `team 2` with only the ability to create audiences and journeys based on `Source Connection 2`.\n\n![](https://files.readme.io/518add0-source_connection_example2.png)\n\n* The first step is locating your Source Connections in the GrowthLoop platform.\n* Navigate to the Organization management panel on the left menu rail. Note, you must have administrator privileges to do this. If you don't see the `Settings` section in left menu , it means your Organization administrator has not give you those permissions. You should contact them to add this permission for you.\n\n![Click on Organization under Settings ](https://files.readme.io/a7aa80d-source_connection_left_menu.png)\n\nClick on Organization under Settings\n\n* On the `Organizations Management Panel`, click on the `Source Connections` tab.\n\n![](https://files.readme.io/ab7a6b3-source_connection_tab.png)\n\n* Here you can view your Source Connections.\n\n![View your Source Connections](https://files.readme.io/bcbfe8c-source_connection_view_list.png)\n\nView your Source Connections\n\n* Create a new Source Connection from the `Source Connection` tab on the `Organization Management Panel` by clicking the button `New Source Connection`\n* Select your Data Cloud\n\n![](https://files.readme.io/c6626c8-new_source_connection_choice.png)\n\n* Insert credentials and wait for validation. We'll let you know if there are any missing permissions to the credentials you provide.\n\n![](https://files.readme.io/0595750-new_source_connection_valid.png)\n\n* Congratulations, you can now see your newly created `Source Connection` on the `Source Connection` tab.\n\n![](https://files.readme.io/936dda1-source_connection_table.png)\n\n> 📘\n> \n> By default your new `Source Connection` is available to all `Teams` in your organization. If you'd like to ensure the `Source Connection` is only usable by specific teams, see how to assign it to teams below.\n\nYou can restrict access to a `Source Connection` by assigning it to be used by specific `Teams` within GrowthLoop. Here is how:\n\n* Navigate to the `Source Connection` tab on the `Organization Management Panel`\n* Click the `Source Connection` row in the table where you would like to assign teams.\n* Under \"Select teams\" section you will see `Teams` are already selected. You can modify which teams have access to this `Source Connection` by deselecting and selecting specific teams.\n\n![](https://files.readme.io/47e2176-edit_source_connection.png)\n\n* Click Save.\n* Congratulations, you've restricted who has access to this `Source Connection`\n\nGrowthLoop automatically updates your Source Connection schemas every day. This means, any new fields for configured datasets will appear automatically for filtering when creating audiences and journeys. It also means, that any new tables will be added so your teams can configure them in a `Dataset Group` to be used in audiences and journeys. But, what if you want to have your source connection refreshed this instant? You can refresh schema in GrowthLoop.\n\n* Navigate to the `Source Connection` tab on the `Organization Management Panel`\n* Scroll to `Last Schema Refresh` column.\n* You can view when exactly your `Last Schema Refresh` occurred.\n* Click the \"Refresh\" icon to refresh your schema immediately.\n* This will update all field and table changes for your `Source Connection` and will make new fields available to your marketers if there is a `Dataset Group` already setup for audience and journey building. It will also make new `tables` available on the `Dataset Group` page so you can include them in audience and journey building.\n* **Note:** Schema refresh can take up to 15 minutes depending on the size of your schema. You will see updates in the Source Connections table when it is finished.\n\n![](https://files.readme.io/5d388b6-source_connection_list_refresh.png)\n\nFor more information or to provide feedback to the team, please reach out to [support@growthloop.com.](mailto:support@growthloop.com.) We can’t wait to hear from you!\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:22.266Z","ed35f207-f013-4429-93f6-06ff000f4a71",[],[],{"_40":1626,"_128":1627,"_130":1628,"_132":1629,"_134":-5,"_13":-5,"_120":1630,"_122":136,"_25":1631,"_138":-5,"_139":1632,"_141":1633},"Sync Data to Marketo | GrowthLoop Docs","sync-data-to-marketo-growthloop-docs","https://docs.growthloop.com/docs/marketo-syncs","Enhance your Marketo campaigns with powerful customer data from your data warehouse.\n\nIn this guide, we’ll walk you through syncing customer data from your data warehouse into Marketo to enhance your customer engagement. Let's get started!\n\nGrowthLoop enables syncing to these Marketo objects:\n\n| Object | Description | Sync Modes | Field Mappings (Required) | Field Mappings (Optional) |\n| --- | --- | --- | --- | --- |\n| `Lead` | Create, enrich, and update lead profiles with additional information | Insert (adds new leads)

Update (modifies existing lead records)

Upsert (combines insert and update functionality) | `Marketo GUID`: This is a unique identifier assigned to each lead record within Marketo

OR

`Email`: Email address of each lead | * \\*Basic Information\\*\\*: `First Name`, `Last Name`,`Title`, `Company`
* \\*Lead Scoring and Qualification\\*\\*: `Lead Score`, `Lead Status`
* \\*Custom Fields\\*\\*: Include any additional data related to leads that you define! |\n| `Custom Objects` | Track unique information related to interactions, transactions, or other custom attributes relevant to your business | Insert (adds new entry)

Update (modifies existing entry)

Upsert (combines insert and update functionality) | `Unique Identifier`: A field that uniquely identifies each entry | * \\*Custom Fields\\*\\*: Include any additional data related to the object that you define! |\n\n \n\n* Ensure you have an active Marketo account and have configured it as a destination. Click [here](https://docs.growthloop.com/docs/marketo) to learn how.\n\n1. Navigate to the **Syncs** tab on the left sidebar and click **Create Sync** in the top right corner.\n2. Set up your Sync with the following details:\n 1. **Sync Name:** A clear, friendly name for your sync.\n 2. **Sync Frequency:** How often data should sync to the destination.\n 3. **Update Rule:** The default method for syncing data to the destination.\n 4. **Dataset / Table:** The table containing your events or user data.\n 5. **Match Field:** The column used to identify users in your source table for the destination system.\n 6. **Dataset Unique Field:** The column with unique values for each user in the table.\n 7. **Connection:** Choose the destination for syncing data. Select **Marketo**.\n 8. **Object Type:** Choose the data object to sync: `Lead` or any custom object. Note that custom object types should be created in Marketo first.\n 9. **Match Field:** The column used to match and identify users in the destination system based on your source data.\n3. After selecting or inserting the required fields, click **Save Sync**.\n4. Next, add field mappings based on the object you're syncing to. For the `Lead` object, map either `Marketo GUID` or `Email`.\n5. To map a field, choose the column that represents `Email` from the **Source** drop-down\n6. In the **Destination** section, select **Email Address**.\n7. To map more fields, click **Add Mapping** to create a new **Source -> Destination** row.\n8. Repeat these steps to map as many standard or custom fields as needed. For a list of Marketo standard fields, refer to the [Marketo API documentation](https://developers.marketo.com/rest-api/lead-database/fields/list-of-standard-fields/).\n9. After mapping all the fields, clicking **Update Sync** will prompt you with the following two options:\n 1. **Updates Only**: We recommend you go with the this option, especially if you’re setting up the sync for the first time.\n 2. **Back-fill**: This option is when you are updating an existing Sync with newly mapped fields and you’d like all your **already synced events** to have those fields backfilled for them. This operation can be very expensive and time consuming on your underlying Data Warehouse, so please choose that option if you’re absolutely sure.\n10. Finally, click the **toggle** at the top of the page to enable!\n\n> 👍\n> \n> You have successfully created a `Lead` sync to Marketo!\n\nUpdated 5 months ago\n\n* * *\n\nLearn how you can send your audiences from GrowthLoop to Marketo.\n\n* [Marketo](https://docs.growthloop.com/docs/marketo)","2024-04-04T17:31:00.897Z","feb263b0-e184-4bbc-9a49-114a6fc15000",[],[],{"_40":1635,"_128":1636,"_130":1637,"_132":1638,"_134":-5,"_13":-5,"_120":1639,"_122":136,"_25":1640,"_138":-5,"_139":1641,"_141":1642},"Sync event data with Tealium | GrowthLoop Docs","sync-event-data-with-tealium-growthloop-docs","https://docs.growthloop.com/docs/tealium","# Sync event data with Tealium\n\nIn this article, we will walk you through the steps to connect Tealium as a destination in the GrowthLoop web application. Once connected, you will be able to send your audience segments to Tealium for marketing activation!\n\nBefore you begin this process, you must have a Tealium account. If you don't, click [here](https://tealium.com/cdh-demo-2/) to request a demo from a Tealium Representative.\n\n1. When you sign into the GrowthLoop Platform, navigate to the **Destinations** tab on the left sidebar and click **New Destination** in the top right corner.\n \n ![](https://files.readme.io/dbbfbe2-Untitled.png)\n2. When the **Select Destination Platform** window pops up, type **Tealium** into the Search Bar and then click **Add Tealium**.\n \n\n![](https://files.readme.io/a12aed9-Untitled_1.png)\n\n3. Clicking **Add Tealium** will require you to select/insert the following information:\n\n![](https://files.readme.io/865215f-Untitled_2.png)\n\n* Destination Info:\n * **Destination Name:** This is how the destination will be named and referred to in to the app going forward. It is helpful to make this name “marketer friendly” so everyone on your team knows it’s purpose.\n * **Sync Frequency**: This is the default frequency audiences will be synced to a destination. Marketers can always change the frequency of an export to Tealium, but this sets the default.\n* Credentials:\n * **Account:** The name of your Tealium account. It can be found in the URL you use to access Tealium.\n * **Profile:** The name of your Tealium profile. It can be found or created as follows:\n 1. Click **Manage Profiles** to open the dialog.\n 2. On the left, click **\\+ Add** to open the **Create Profile** dialog.\n 3. Enter a name (up to 50 characters) using only a-z, 0-9, \".\", and \"-\".\n 4. Use the **+** button to add more profile names if needed.\n 5. Select items in **Copy Elements From** to transfer to the new profile.\n 6. Click **Create Profile** to finalize.\n * **Data source key**: The data source key from Customer Data Hub. You can find it by following these steps:\n 1. Navigate to the **Sources** section in the sidebar and select **Data Sources**.\n 2. Click on the name of the specific data source you want to use. This will expand the details for that data source.\n 3. Within the expanded view, locate the field labeled **Data Source Key**. The value displayed in this field is your unique data source key.\n\n4. Go ahead and select **Create**, and we’ll validate we have all the proper permissions to load audience data to Tealium. You should now see **Tealium** in your list of connected destinations!\n\n![](https://files.readme.io/d3d16dd-Untitled_3.png)\n\n> 📘\n> \n> If you experience any issues when connecting to Tealium, please reach out to us at [support@growthloop.com](mailto:support@growthloop.com), and we’ll be in touch shortly to help resolve the matter!\n> \n> If you're looking for other helpful how-to’s for connecting your favorite marketing and sales destinations, [Click here](https://www.flywheelsoftware.com/help-center-categories/destinations) to find more in our Help Center!\n\nUpdated 5 months ago\n\n* * *","2024-04-10T18:41:40.819Z","76dd65a0-a6e1-40fd-a418-51e97ee3c078",[],[],{"_40":1644,"_128":1645,"_130":1646,"_132":1647,"_134":-5,"_13":-5,"_120":1648,"_122":136,"_25":1649,"_138":-5,"_139":1650,"_141":1651},"Tealium Event Sync","tealium-event-sync","https://docs.growthloop.com/docs/tealium-event-sync","Enhance Tealium with powerful customer data from your data warehouse.\n\nIn this guide, we’ll walk you through syncing customer data from your data warehouse into Tealium for enhanced analytics and personalized marketing efforts. Let's get started\n\nGrowthLoop enables syncing to the Visitor object.\n\n| Object | Description | Sync Modes | Field Mappings (Required) | Field Mappings (Optional) |\n| --- | --- | --- | --- | --- |\n| `Visitors` | Represents the individual visitors to the site | Upsert (inserts new data if it doesn't exist or updates existing data if a matching record is found) | `Visitor ID`: Unique identifier assigned to each individual who interacts with a website or application | * \\*Basic Information\\*\\*:`First Name`, `Last Name`, `IP Address`, etc.
* \\*Custom Fields\\*\\*: Include any additional data related to visitors that you define! Make sure the custom fields already exist in Tealium |\n\n* Make sure you have a Tealium account. If you don't click [here](https://tealium.com/cdh-demo-2/) to request a demo from a Tealium Representative.\n* Connect Tealium as a destination to your GrowthLoop account. Click [here](https://docs.growthloop.com/docs/tealium) for detailed instructions.\n\n1. Navigate to the **Syncs** tab on the left sidebar and click **Create Sync** in the top right corner.\n2. Set up your Sync with the following details:\n 1. **Sync Name:** A clear, friendly name for your sync.\n 2. **Sync Frequency:** How often data should sync to the destination.\n 3. **Update Rule:** The default method for syncing data to the destination. `Upsert` is the only supported mode.\n 4. **Dataset / Table:** The table containing your user or event data.\n 5. **Match Field:** The column used to identify users in your source table for the destination system.\n 6. **Dataset Unique Field:** The column with unique values for each user in the table.\n 7. **Connection:** Choose the destination for syncing data. Select **Tealium**.\n 8. **Object Type:** Choose the data object to sync: `Visitor`\n 9. **Match Field:** The column used to match and identify users in the destination system based on your source data. Please select `visitor_id`\n3. After selecting or inserting the required fields, click **Save Sync**.\n4. Next, add your desired field mappings. For the `Visitor` object, Tealium requires at least one field linked to the `visitor_id`.\n5. To map the field, choose the column that represents `visitor_id` from the **Source** drop-down\n6. In the **Destination** section, select **visitor\\_id**.\n7. To map more fields, click **Add Mapping** to create a new **Source -> Destination** row. Note:\n\n> 📘\n> \n> You can map any attribute from your source table to Tealium by typing the attribute name directly into the destination drop-down. Just remember, the Visitor attribute must already exist in Tealium. If you need to create new attributes, you can learn how to do so by clicking [here](https://docs.tealium.com/server-side/attributes/manage-attributes/add-attribute/).\n\n8. Repeat these steps to map as many standard or custom fields as needed.\n9. After mapping all the fields, clicking **Update Sync** will prompt you with the following two options:\n 1. **Updates Only**: We recommend you go with the this option, especially if you’re setting up the sync for the first time.\n 2. **Back-fill**: This option is when you are updating an existing Sync with newly mapped fields and you’d like all your **already synced events** to have those fields backfilled for them. This operation can be very expensive and time consuming on your underlying Data Warehouse, so please choose that option if you’re absolutely sure.\n10. Finally, click the **toggle** at the top of the page to enable!\n11. To confirm that your event data has been successfully sent to your Tealium account, navigate to the **AudienceStream** section in your **Tealium Customer Data Hub** and select **Visitor** to view updated attributes.\n\n![](https://files.readme.io/00393e3-image.png)\n\n> 👍\n> \n> You have successfully created a `Visitor` sync to Tealium!\n\n> 📘\n> \n> If you experience any issues, please reach out to us at [support@growthloop.com](mailto:support@growthloop.com) , and we’ll be in touch shortly to help resolve the matter!\n\nUpdated 5 months ago\n\n* * *\n\nLearn how you can send your audiences from GrowthLoop to Tealium.\n\n* [Tealium](https://docs.growthloop.com/docs/tealium)","2024-04-24T23:07:51.821Z","233404d2-94f9-453b-9636-3391f206cbdd",[],[],{"_40":1653,"_128":1654,"_130":1655,"_132":1656,"_134":-5,"_13":-5,"_120":1657,"_122":136,"_25":1658,"_138":-5,"_139":1659,"_141":1660},"The composable approach to data activation | GrowthLoop Docs","the-composable-approach-to-data-activation-growthloop-docs","https://docs.growthloop.com/docs/overview-1","# The composable approach to data activation\n\n## Overview\n\nLearn how to activate to destinations\n\nThe entire purpose of a composable audience and journey platform is to enable your teams to more effectively use the activation marketing and sales tools they already love from Salesforce to Facebook Ads. The transformative effect of composable, is that now the **activation marketing and sales tools can now be orchestrated from a central hub**. This leads to coordination between teams, a more cohesive customer experience, faster campaign experimentation, and as a result: faster growth.\n\nA composable approach to audiences and journeys also unlocks a major benefit for the future of your go to market organization: Innovation. Your teams can select new best of breed marketing and sales tools for your stack and hydrate them with audiences and orchestrate them in journeys in 90% less time than a traditional martech stack.\n\nGrowthLoop supports every major marketing and sales destination, and is adding new destinations each month. If you don't see your destination listed please contact [solutions@growthloop.com.](mailto:solutions@growthloop.com.) If it is not already supported, we can typically add it within 2 weeks of the request.\n\n![](https://files.readme.io/4ac1a14-Screenshot_2024-01-25_at_9.54.54_AM.png)\n\n> 📘\n> \n> GrowthLoop was purpose built for enterprise. We support dozens of custom destinations at our enterprise clients. Have your own email or sms tool you built internally? Our destination architects can get you setup following our [Custom Destination integration patterns](https://docs.growthloop.com/docs/custom-destinations-copy) and make any customizations necessary.\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:36.246Z","79be2938-2ed8-4366-bfaf-2009e8b0e358",[],[],{"_40":1662,"_128":1663,"_130":1664,"_132":1665,"_134":-5,"_13":-5,"_120":1666,"_122":136,"_25":1667,"_138":-5,"_139":1668,"_141":1669},"The GrowthLoop platform: An overview | GrowthLoop Docs","the-growthloop-platform-an-overview-growthloop-docs","https://docs.growthloop.com/docs/welcome","# The GrowthLoop platform: An overview\n\n## Welcome\n\nA quick overview of the GrowthLoop platform\n\nGrowthLoop is a platform designed to revolutionize data-driven marketing by empowering marketers to leverage customer data efficiently and effectively. Below are the core concepts and features that define GrowthLoop:\n\n![](https://files.readme.io/c566424-65529a8039778f70c512977a_Group_3090_4-p-2000.png)\n\n**Composable customer data platform (CDP):** GrowthLoop functions as a composable CDP, enabling marketers to build customer segments in a unified audience layer, orchestrate journeys across channels, and measure results directly on their data cloud.\n\n**No-code data activation:** The platform allows for activating first-party data without SQL or coding. This democratizes the ability for marketers to create cross-channel audiences, reducing time to launch and fostering innovation.\n\n**Intelligent customer segments:** GrowthLoop aids in creating intelligent customer segments for personalized campaigns, enhancing the customer experience. It recommends audience segments based on machine learning and the data models provided.\n\n**Revenue lift measurement:** A simple dashboard is provided to view the incremental lift on key metrics for each customer audience, enabling effective measurement of marketing strategies.\n\n**Generative and adaptive capabilities:** The platform supports the generation of results with intelligent audience segments and targeted campaigns. It allows for the adaptation of strategies through comprehensive measurement across all channels.\n\nLearn about what a composable CDP is - [What is a composable CDP?](https://www.growthloop.com/university/article/composable-cdp)\n\nLearn about what Generative Marketing is - [Generative Marketing](https://www.growthloop.com/university/article/generative-marketing)\n\nLearn how to activate your data from your warehouse to marketing tools within five minutes.\n\nUpdated 5 months ago\n\n* * *\n\n* [Core Concepts](https://docs.growthloop.com/docs/core-concepts)","2024-03-20T21:02:38.022Z","fa7b1bcc-343b-4e73-b319-d69323fb0b28",[],[],{"_40":1671,"_128":1672,"_130":1673,"_132":1674,"_134":-5,"_13":-5,"_120":1675,"_122":136,"_25":1676,"_138":-5,"_139":1677,"_141":1678},"TikTok event syncs | GrowthLoop Docs","tiktok-event-syncs-growthloop-docs","https://docs.growthloop.com/docs/tiktok-syncs","## TikTok Conversions\n\nLearn how to create Syncs for TikTok conversions\n\nIn this guide, we’ll walk you through syncing web event data from your data warehouse into TikTok to supercharge your marketing efforts. Let's get started!\n\nGrowthLoop enables syncing to the following TikTok object:\n\n| Object | Description | Sync Modes | Field Mappings (Required) | Field Mappings (Optional) |\n| --- | --- | --- | --- | --- |\n| `Web Event` | Sync and track actions users take on your website, like purchases, form submissions, or adding items to a cart | Insert (adds new events) | `Event name`: The event’s name

`Timestamp`: When the event occurred in Unix timestamp format

`Event ID`: The unique identifier for each event instance

`Page URL`: Where the event occurred | See full list of parameters [here](https://ads.tiktok.com/gateway/docs/index?identify_key=2b9b4278e47b275f36e7c39a4af4ba067d088e031d5f5fe45d381559ac89ba48&language=ENGLISH&doc_id=1727541103358977#item-link-Supported%20web%20events) |\n\n* Make sure you have a **TikTok Ads Manager** account. You can create one [here](https://ads.tiktok.com/help/article/create-tiktok-ads-manager-account?lang=en)!\n* Connected **TikTok** as a destination to your GrowthLoop account. Click [here](https://docs.growthloop.com/docs/tiktok) for detailed instructions.\n* Created a **Pixel Code**. Access it by logging into your **TikTok Ads Manager** account and navigating to **Tools > Events > Web Events**. If you haven’t created one yet, click [here](https://ads.tiktok.com/help/article/get-started-pixel?lang=en) to learn how.\n\n1. Click **Destinations** on the left sidebar.\n2. Select **TikTok** in your list of connected destinations.\n3. Input your **Pixel Code** in the designated field under **Credentials** and click **Save**.\n4. Now, let's create a Sync. Begin by selecting **Syncs** from the options listed on the left sidebar.\n5. Then click **Create Sync** on the upper right side.\n6. Next, configure your sync by filling out the following fields:\n 1. Route Name:\n 1. **Name:** A friendly name for the sync.\n 2. **Sync Frequency**: The default frequency for syncing data to the destination. The options are: **15 minutes**, **30 minutes**, **hourly**, and **daily**.\n 3. **Update Rule:** The default operation for syncing data to the destination. TikTok supports only the **Insert** rule, which means new data is added to the destination without updating or overwriting existing data.\n 2. Source:\n 1. **Dataset/Table:** The table that holds the data you want to sync to TikTok. Usually, it's organized within an events table.\n 2. **Dataset Unique Field(s):** The unique field(s) on the table. They will populate automatically after selecting the Dataset/Table.\n 3. **Match Field**: The column in your source table that is used to match data to TikTok. Please select your email field.\n 3. Destination:\n 1. **Connection:** The destination you will sync data to. Please select **TikTok**.\n 2. **Object Type:** Select the type of object you want to send data to. Currently, only Web Events are supported, but Offline, App, and CRM options will be available in the near future. Please choose **Web Events**.\n 3. **Match Field:** Choose the column in TikTok that corresponds to the email field in your source dataset.\n7. Once you finish selecting/inserting the required fields, click **Save Route**.\n8. Next, set up the field mappings to start your sync. TikTok Web Events needs at least four of the following fields mapped: **Event Name**, **Event Time**, **Event ID**, and **Page URL.**\n9. Let's begin with **Event Name**. Choose the field from your table that contains the name of your conversion event. \n **Note:** TikTok supports both Standard Events and Custom Events. See a list of standard event names [here](https://business-api.tiktok.com/portal/docs?id=1771101186666498).\n10. Then, under the Destination section, choose **Event Name** from the drop-down menu, unless it has been automatically selected for you.\n11. Next up, let’s map **Event Time**. Pick the field from your table that holds the time when the event occurred.\n12. Then, under the Destination section, choose **Event Time** from the drop-down menu, unless it has been automatically selected for you.\n13. Now, let’s map **Event ID.** Pick the field from your table that holds the ID that is used to identify a unique event.The data type of the field should be a `STRING` and it should be in Unix timestamp format.\n14. Then, under the Destination section, choose **Event ID** from the drop-down menu, unless it has been automatically selected for you.\n15. Lastly, choose the field in your source table that contains the **Page URL** of where the event occurred, and map it to the destination. TikTok recommends to use the full URL, including all URL parameters.\n16. After clicking **Update Route**, return to your sync and enable it by clicking the toggle at the top of the page!\n\n> 👍\n> \n> You've successfully created a web sync to TikTok! You should now be able to see it in your Syncs table.\n\nTo confirm that your web event data has been received, log in to your **Ads Manager** account, navigate to the **Tools** tab, select **Events**, and click the **Manage** button under **Web Events**.\n\n![](https://files.readme.io/59a0195-image.png)\n\n> 📘\n> \n> If you experience any issues when connecting to or creating syncs to TikTok, please reach out to us at [support@growthloop.com](mailto:support@growthloop.com), and we’ll be in touch shortly to help resolve the matter!\n\nUpdated 5 months ago\n\n* * *","2025-06-20T22:58:02.792Z","aef87e5c-267e-4e39-8308-7cbd278e0367",[],[],{"_40":1680,"_128":1681,"_130":1682,"_132":1683,"_134":-5,"_13":-5,"_120":1684,"_122":136,"_25":1685,"_138":-5,"_139":1686,"_141":1687},"Trigger an audience export snapshot","trigger-an-audience-export-snapshot","https://docs.growthloop.com/reference/post_api-public-exports-id-snapshot","Language\n\nCredentials\n\n \\--url https://app.pub.prod.flywheelproducts.com/api/public/exports/id/snapshot \\\\\n\n \\--header 'accept: application/json'\n\nClick `Try It!` to start a request and see the response here! Or choose an example:","2025-10-23T18:21:53.157Z","da84ff01-8e66-4f1c-b041-56da55e7bdc8",[],[],{"_40":1689,"_128":1690,"_130":1691,"_132":1692,"_134":-5,"_13":-5,"_120":1693,"_122":1693,"_25":1694,"_138":-5,"_139":1695,"_141":1696},"Understanding the 'audience_id' Column in Exported Audiences","understanding-the-audienceid-column-in-exported-audiences","https://growthloop.unthread.io/dashboard/inbox/all/conversations/49a4dd6c-05c2-4e6a-961b-6873eae66cd2","**Overview:**\n\nWhen exporting audiences to TransUnion, the resulting dataset includes a column labeled `audience_id`. This column is significant for identifying individual audiences within the export.\n\n**Details:**\n\n- The `audience_id` column contains a unique identifier for each audience.\n- Currently, these identifiers are five-digit numbers. However, as more audiences are added, the identifiers may expand to six or seven digits.\n\n**Implications for TransUnion Ingestion:**\n\n- TransUnion should expect numeric values in the `audience_id` column.\n- These values correspond directly to the unique identifiers assigned to each audience during the export process.\n\n**Conclusion:**\n\nUnderstanding the structure and content of the `audience_id` column ensures seamless integration and data processing for exported audiences. If further clarification is needed, please reach out to the support team.","2026-01-27T19:36:07.514Z","013e3185-41c3-4473-976d-30acafe067e6",[],[],{"_40":1698,"_128":1699,"_130":1700,"_132":1701,"_134":-5,"_13":-5,"_120":1702,"_122":136,"_25":1703,"_138":-5,"_139":1704,"_141":1705},"Unlock Braze with a Composable CDP | GrowthLoop Docs","unlock-braze-with-a-composable-cdp-growthloop-docs","https://docs.growthloop.com/docs/integrate-braze","# Unlock Braze with a Composable CDP\n\n## Integrate with Braze\n\nIn this article, you'll learn how to integrate GrowthLoop with Braze\n\nGrowthLoop helps you unlock the best of Braze. In this guide, we'll walk you through how GrowthLoop and Braze integrate, and how that can help you unlock value faster for your teams.\n\n![](https://files.readme.io/e47164f-growthloop__braze.png)\n\nBraze is an excellent platform for creating and delivering mobile messages and email to your customers. By coupling Braze with a composable CDP like GrowthLoop, you will:\n\n1. **Unlock Braze faster** for your marketing teams\n2. **Remove the need to copy all data** to Braze to unlock its full capability set. By keeping your data centralized in your data cloud, and only sending Braze what it needs you will increase privacy, and decrease the need for costly data pipelines.\n3. **Measure** all audiences used in Braze in a central location\n4. **Decrease overall costs**\n5. Enable marketing to use **any Channels or Tools alongside Braze** seamlessly.\n\nA great way to see the power of having a composable CDP integrated with Braze is to leverage GrowthLoop audiences to trigger Braze Campaigns. You can define audiences directly on your data cloud to trigger Braze Campaigns in any Braze supported channel including email, sms, push notification, in app messaging, and content cards.\n\n![](https://files.readme.io/cde57ca-braze_campaigns.png)\n\nBefore we walk through how this setup works, let's review the key reasons customers choose this approach:\n\n* Marketing teams can use audiences across 100+ marketing channels alongside Braze.\n* Marketing teams can use \"All\" our organization's data when defining audiences without ever having to copy it to Braze.\n* Marketing teams can use our data science team's predictions to define audiences.\n* Marketing teams can use internal data like coupon assignments, and experiment labels in our Braze campaigns.\n* Data teams can access all audiences used in Braze instantly in our data cloud.\n* Data teams can verify and analyze audience impact directly in our data cloud.\n* For global organizations, not all regions have to use Braze, but they can still leverage the same audiences in their marketing tools.\n\n![](https://files.readme.io/899b579-GL_Braze_Extra_Channels.png)\n\nYou can begin using GrowthLoop audiences to trigger Braze campaigns in three simple steps:\n\n1. Create an Audience in GrowthLoop\n2. Export the Audience to Braze.\n3. Configure your Braze Campaign to use the GrowthLoop Audience.\n\n**Let's break this down a bit further for how to do it in the tools:**\n\n1. Create an Audience in GrowthLoop\n \n 1. From GrowthLoop Home, click Audiences in left-hand menu.\n 2. Select \"Create Audience\"\n 3. Create an audience by applying filters to target the customers you would like and click \"Save\"\n2. Export the Audience to Braze.\n \n 1. Select \"Export\" in the upper right of the audience menu\n 2. Select Braze Destination and provide \"Export Name\". This \"Export Name\" will be the Segment name in Braze that you are able to select for your Braze Campaign.\n 3. Select your \"Export Frequency\" and personalization fields.\n 4. Select \"Export\". Congratulations, your audience is now on its way to Braze and will stay in Sync.\n3. Configure your Braze Campaign to use the GrowthLoop Audience.\n \n 1. Navigate to Braze, and create Braze Campaign\n 2. Select the type of Campaign: Email, SMS, Push, or Content Card\n 3. Select Delivery Type \"Scheduled\"\n 4. Select [\"Send at Designated Time\"](https://www.braze.com/docs/user_guide/engagement_tools/campaigns/building_campaigns/delivery_types/scheduled_delivery/) or \"Intelligent Timing\"\n 5. If you select \"Intelligent Timing\" Braze will automatically choose a time during that day that optimizes for when customers engage with that campaign type.\n 6. If you select \"Send at Designated Time\", select Entry Frequency of Daily or Hourly.\n 7. [Under Target Audience](https://www.braze.com/docs/user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/?tab=api-triggered%20delivery), select \"Filters\" dropdown.\n 8. Select the GrowthLoop Audience Name, and select `is True`\n 9. Save and Launch Braze Campaign\n \n ![](https://files.readme.io/07e762b-braze_targeting_small.png) \n \n\nCongratulations, you are now sending Braze campaigns based on an audience defined directly in your data cloud using GrowthLoop.\n\nA common usage pattern is to use GrowthLoop audiences to target your Braze Journey sequences. Here is how you can use GrowthLoop audiences to target your Braze Canvas to orchestrate journeys across your Braze channels: Email, SMS, In App Message, Push, and Content Cards.\n\n![](https://files.readme.io/de5b8e0-braze_canvas.png)\n\nThis approach can help reduce cost while unlocking the power of your data cloud for targeting your Braze Canvas journeys. Here are a [few key reasons why customers](https://docs.growthloop.com/docs/integrate-braze#why-use-growthloop-audiences-to-trigger-braze-campaigns) choose this approach.\n\nYou can begin using GrowthLoop audience to trigger Braze campaigns in three simple steps:\n\n1. Create an Audience in GrowthLoop\n2. Export the Audience to Braze.\n3. Create Braze Canvas and target your GrowthLoop Audience.\n\n**Now let's break this down a bit further for how to do it in the tools:**\n\n1. Create an Audience in GrowthLoop\n 1. Follow the steps in this [section](https://docs.growthloop.com/docs/integrate-braze#how-to-use-growthloop-audiences-in-braze-campaigns) to create your GrowthLoop Audience\n2. Export your Audience to Braze\n 1. Follow the steps in this [section](https://docs.growthloop.com/docs/integrate-braze#how-to-use-growthloop-audiences-in-braze-campaigns) to export your GrowthLoop Audience to Braze\n3. Create Braze Canvas and target your GrowthLoop Audience.\n 1. In Braze, [create a new Braze Canvas](https://www.braze.com/docs/user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/)\n 2. [Under Entry Schedule](https://www.braze.com/docs/user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/#step-2b-determine-your-canvas-entry-schedule), select \"Scheduled\"\n 3. Select \"Enter users at a Designated Time\"\n 4. Select \"Entry Frequency\" of \"Daily\" with entry time.\n 5. [Under Target Audience](https://www.braze.com/docs/user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/?tab=api-triggered%20delivery), select \"Filters\" dropdown.\n 6. Select the GrowthLoop Audience Name you would like to target your Journey to, and select `is True`\n 7. Create your [messaging sequence](https://www.braze.com/docs/user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/) on Braze Canvas\n 8. Confirm your \"Total Reachable Users\" for your Braze Canvas matches the size of your GrowthLoop user to ensure everything is working properly prior to launch.\n 9. [Save and Launch](https://www.braze.com/docs/user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/#step-5-save-and-launch-your-canvas) your Braze Canvas\n\nCongratulations, you are now targeting Braze Canvas Journeys to audiences defined directly in your data cloud using GrowthLoop. New users will continue to flow through your journey as they enter the GrowthLoop audience.\n\nOften time customers want to centralize their journey orchestration logic closer to their data. In this setup you will be using GrowthLoop Journeys instead of Braze Canvas to orchestrate your journeys.\n\n![](https://files.readme.io/1c761bb-GL_Journeys.png)\n\nThere are several key benefits to having your journeys live in a Composable CDP.\n\n* Marketing teams orchestrate journeys in 100+ marketing channels alongside Braze.\n* Marketing teams can use \"All\" your organization's data when defining each step in your journey paths.\n * Want to use your latest survey data?\n * How about your latest purchase data in store?\n* Marketing teams can use your data science teams predictions to trigger users to enter a journey.\n* Data teams can see every journey and step a user is in at all times.\n* Data teams can verify and analyze journey impact directly in your data cloud.\n* **Marketer Choice:** As a global organization, not all regions have to use Braze, but they can still leverage the same journey builder in their marketing tools.\n* **Avoid Lockin**: Organizations can avoid getting locked-in to an individual MarTech tool. Your journeys are portable and you own the data with GrowthLoop.\n\n![](https://files.readme.io/0826dee-GL_Braze_Journeys_Extra_Channels.png)\n\nYou can begin using Braze to send messages in GrowthLoop Journeys in a few simple steps.\n\n1. Create a Journey in GrowthLoop.\n2. Add Braze Destination to GrowthLoop Journey.\n3. Create Braze Campaign and Link to GrowthLoop Journey.\n4. Publish GrowthLoop Journey.\n\n**Detailed Instructions:**\n\n1. Create a Journey in GrowthLoop.\n 1. From GrowthLoop Home, click on Journeys in left hand menu\n 2. Click Create Journey\n 3. Insert Journey Settings\n2. Add Braze Destination to GrowthLoop Journey.\n 1. Drag out Destination Node\n 2. Click \"Settings on Destination Node menu\n 3. Select Braze as Destination\n 4. Insert Export Name. Note, this will be the name of the audience you select in your Braze Campaign below.\n3. Create Braze Campaign and Link to GrowthLoop Journey.\n 1. Navigate to Braze\n 2. Create Braze Campaign\n 3. Select type of Campaign: Email, SMS, Push, Content Card\n 4. Select Delivery Type \"Scheduled\"\n 5. Select [\"Send at Designated Time\"](https://www.braze.com/docs/user_guide/engagement_tools/campaigns/building_campaigns/delivery_types/scheduled_delivery/) or \"Intelligent Timing\"\n 6. If you select \"Intelligent Timing\" Braze will automatically choose a time during that day that optimizes for when customers engage with that campaign type.\n 7. If you select \"Send at Designated Time\"\n 8. Select Entry Frequency of Daily or Hourly.\n 9. [Under Target Audience](https://www.braze.com/docs/user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/?tab=api-triggered%20delivery), select \"Filters\" dropdown.\n 10. Select the GrowthLoop Audience Name you created in the Journey Destination Node above, and then select `is True`\n 11. Save and Launch Braze Campaign\n4. Publish your GrowthLoop Journey.\n 1. Navigate to GrowthLoop Journey\n 2. Click Publish\n\nCongratulations, now GrowthLoop will guide users through journey, and when they are sent to Braze users will automatically receive your Braze campaign at the right step within the journey.\n\nGrowthLoop supports **Syncs** to Braze. This enables you to bring data from your data cloud to Braze for use in the platform. This is typically where teams get started with the integration between a Composable CDP and Braze. However, teams are often tempted to overuse this capability and try to sync **too much customer data** to Braze from their data cloud. This can create cost and privacy implications.\n\nInstead, we highly recommend your teams only start with syncing at most **20 Attributes** from your data cloud to Braze. The best practice is to only sync attributes from your data cloud to Braze that are used often in personalization of message content.\n\nGrowthLoop syncs data to the contact object in Braze. Once synced, it can be used in:\n\n* **Audience Targeting:** You can leverage data on user record as filters in Audience Targeting for campaigns.\n* **Personalization:** You can leverage data on user record as personalization fields in your Braze Campaign creative.\n\n![](https://files.readme.io/b3d5490-GL_Syncs.png)\n\nTo see in-depth instructions on how to setup syncs from your data cloud to Braze, follow this [Braze Sync guide](https://docs.growthloop.com/docs/braze).\n\nIt can be extremely helpful to have all your email, sms, push and other interaction data from Braze available to your team in your data cloud for use in GrowthLoop audiences and journeys. Now with just a few clicks you can bring your Braze data into your Data Cloud leveraging **GrowthLoop Easy Button**.\n\n![](https://files.readme.io/da64dbe-Braze_Ingest.png)\n\n1. In GrowthLoop, click on Ingest in left-hand menu\n2. Select \"Add Source\" in the upper right.\n3. Select \"Braze\"\n4. Provide your API credentials to access data in Braze.\n5. GrowthLoop will verify these credentials will work to begin pulling data.\n6. Once setup, GrowthLoop will begin syncing data from Braze to your Data Cloud\n\n \n\n1. In GrowthLoop, click on \"Datasets\" in left-hand menu\n2. Select \"Add Dataset\"\n3. Select the Braze table you'd like to utilize when building an audience. Examples include:\n 1. SMS\\_EVENT\n 2. WHATSAPP\\_EVENT\n 3. IN\\_APP\\_MESSAGE\\_EVENT\n 4. EMAIL\\_EVENT\n 5. CONTENT\\_CARD\\_EVENT\n 6. PUSH\\_NOTIFICATION\\_EVENT\n4. In Dataset Configuration, select the tables unique ID\n5. Save Dataset\n6. On \"Datasets\" page, select \"Dataset Groups\" tab.\n7. Select the \"Dataset Group\" you' would like to add your Braze event dataset to use in audience and journey building.\n8. Define join key between \"Dataset\" and the \"Primary Dataset\" in the Dataset Group\n9. Click Save\n10. Select \"Audiences\" in left-hand menu\n11. Select \"New Audience\"\n12. Select Dataset Group you just added Braze Dataset to begin building your audience.\n13. You can now see you can leverage your Braze Dataset in building your audience in GrowthLoop and export to any paid media, crm, or marketing channel. You can use your Braze dataset to design audiences that:\n 1. Haven't interacted with email in past 90 days\n 2. Opened a specific email more than once.\n 3. Interacted with a Content Card about a new product in your app.\n\n \n\n1. Follow Steps 1-10 in the section above.\n2. From GrowthLoop Home, select \"Journeys\" in left hand menu\n3. Select \"New Journey\"\n4. Insert your Journey Settings and click Save\n5. Drag a Criteria Node out onto the Journey Canvas\n6. Select Settings on Criteria Node Menu\n7. Add your Braze events dataset to the Criteria Node to use it as a criteria in your journey. For example, you can target:\n 1. Users in the journey who opened the email sent in previous step\n 2. Users in journey who haven't opened an email in 90 days, and send them to Facebook Ads.\n\nCongratulations, you are now using data generated by Braze to build audiences and journeys in your GrowthLoop Composable CDP.\n\nUpdated 5 months ago\n\n* * *","2025-06-20T22:58:49.295Z","bc7bd4b9-bf70-4b90-96ab-a29658b19e4e",[],[],{"_40":1707,"_128":1708,"_130":1709,"_132":1710,"_134":-5,"_13":-5,"_120":1711,"_122":136,"_25":1712,"_138":-5,"_139":1713,"_141":1714},"update audience","update-audience","https://docs.growthloop.com/reference/patch_api-public-audiences-id","patch https://app.pub.prod.flywheelproducts.com/api/public/audiences/\n\n| time | status | user agent | |\n| --- | --- | --- | --- |\n| Make a request to see history. | | | |\n\nClick `Try It!` to start a request and see the response here! Or choose an example:","2025-06-20T22:59:05.381Z","3ac8f32d-5fd6-47b4-8dff-9f866c84066c",[],[],{"_40":1716,"_128":1717,"_130":1718,"_132":1719,"_134":-5,"_13":-5,"_120":1720,"_122":136,"_25":1721,"_138":-5,"_139":1722,"_141":1723},"update journey","update-journey","https://docs.growthloop.com/reference/patch_api-public-journeys-id","patch https://app.pub.prod.flywheelproducts.com/api/public/journeys/\n\n| time | status | user agent | |\n| --- | --- | --- | --- |\n| Make a request to see history. | | | |\n\nFilter journey to those with this team id\n\nClick `Try It!` to start a request and see the response here! Or choose an example:","2025-06-20T22:59:06.753Z","8c10faf7-024c-4d05-a30d-1be52a07d3a3",[],[],{"_40":1725,"_128":1726,"_130":1727,"_132":1728,"_134":-5,"_13":-5,"_120":1729,"_122":136,"_25":1730,"_138":-5,"_139":1731,"_141":1732},"update journey node","update-journey-node","https://docs.growthloop.com/reference/patch_api-public-journeys-id-nodes-key","patch https://app.pub.prod.flywheelproducts.com/api/public/journeys//nodes/\n\n| time | status | user agent | |\n| --- | --- | --- | --- |\n| Make a request to see history. | | | |\n\nClick `Try It!` to start a request and see the response here! Or choose an example:","2025-06-20T22:59:06.217Z","f1f1dd5b-c74a-42d3-9fca-046f4b414e7f",[],[],{"_40":1734,"_128":1735,"_130":1736,"_132":1737,"_134":-5,"_13":-5,"_120":1738,"_122":136,"_25":1739,"_138":-5,"_139":1740,"_141":1741},"Use data to deploy TikTok campaigns | GrowthLoop Docs","use-data-to-deploy-tiktok-campaigns-growthloop-docs","https://docs.growthloop.com/docs/tiktok","# Use data to deploy TikTok campaigns\n\nLearn how to connect and send audiences to TikTok\n\nIn this article, we'll guide you through connecting **TikTok** to GrowthLoop and exporting your audiences to the destination.\n\nTikTok is an advertising solution that enables brands to reach diverse audiences through engaging, short-form video placements powered by TikTok’s algorithm-driven content discovery.\n\n* Have a registered **TikTok for Business** account. If you don't, fill out this [form](https://ads.tiktok.com/business/en-US/solutions/business-account) to create one!\n* Ensure the person granting GrowthLoop access has either the **Operator** or **Admin** role.\n\n1. Log into **GrowthLoop** and click the **Destinations** tab on the left sidebar.\n \n2. Then click **New Destinations** on the upper right side.\n \n3. Next, search for **TikTok** in the destination modal.\n \n\n> 📘\n> \n> **Note**\n> \n> You’ll see two TikTok destinations in GrowthLoop: `TikTok` (Batch API) and `TikTok Streaming` (Streaming API).\n> \n> * `TikTok`: The Batch API processes audiences in bulk and can take hours before they’re ready, and it lets you mix device IDs in one column.\n> * `TikTok Streaming`: The Streaming API updates audiences almost instantly, but requires device IDs to be mapped separately as AAID or IDFA.\n> \n> For now, both options are available so you can choose the one that best fits your needs.\n\n4. Click **Add**, and you’ll be redirected to TikTok's **Request for Permission** page.\n5. Then, select **Confirm** to grant GrowthLoop access to your TikTok for Business account.\n6. After granting permission, you'll be redirected back to GrowthLoop. Fill out the required fields in the modal and click **Create**:\n 1. `Destination`: Enter the name you want to give the destination.\n 2. `Sync Frequency`: Select a default export frequency to the destination.\n 3. `OAuth Token`: Your TikTok authentication token will auto-populate here.\n 4. `Ad Account`: Select the business account from the drop-down menu where you want to export your audiences.\n 5. `Pixel Code`: Optional. Only needed for sending [web events with Syncs](https://docs.growthloop.com/update/docs/tiktok-syncs#/).\n\n7. Navigate to your list of audiences by clicking the **Audiences** tab on the left sidebar.\n8. Choose an existing audience or create a new one.\n\n> 📘\n> \n> **Note**\n> \n> Need help creating an audience? Click [here](https://docs.growthloop.com/docs/create-an-audience) to learn how!\n\n9. Next, click the **Export** button on the upper right side.\n10. Search for **TikTok** in the export modal and then click **Select**.\n11. Map one of the following user identifiers under **Configure Match Field Settings**:\n 1. `Email`\n 2. `Phone`\n 3. `IDFA`\n 4. `AAID`\n\n> 📘\n> \n> **Note**\n> \n> For **TikTok Streaming**, you’ll see separate match fields for **AAID** (Android) and **IDFA** (iOS). TikTok requires these to be mapped individually for faster and more precise matching. In the standard **TikTok** (Batch) destination, only a single **Mobile Device ID** field is available.\n\n12. Configure your export settings:\n 1. `Export Name`: Automatically populated with your audience name for easy identification in the destination.\n 2. `Campaign Type`: Choose between a `One Time` export or `Ongoing` basis.\n 3. `Export Schedule`: Set the `Frequency`, `Start Date`, `End Date`, and specific `Days of the Week`.\n13. Finally, click **Export** to send the audience to **TikTok**!\n\n> 👍\n> \n> **Success**\n> \n> You have successfully exported an audience!\n\n14. To view your audience, log in to [TikTok Ads](https://ads.tiktok.com/i18n/home), go to **Ads Manager**, and then open the **Audience Manager** section.\n\n> 📘\n> \n> **Note**\n> \n> TikTok customer file audiences expire after `12 months` of inactivity. To keep an audience active, you must apply it to a campaign, modify the file, or use it in a Lookalike within that time.\n\n![](https://files.readme.io/7914c0d4124bee0b75e1cd5f5785275186c09a3a3d4d57c3dd46f8c87fd30cf8-image.png)\n\n> 📘\n> \n> Experiencing any issues when connecting and/or exporting to **TikTok**? Reach out to us at [support@growthloop.com](mailto:support@growthloop.com) and we’ll be in touch shortly to help resolve the matter!\n\nUpdated about 2 months ago\n\n* * *","2024-03-20T21:02:30.306Z","bc2db1f1-f3d9-4a5c-b7c9-7cb3558399b7",[],[],{"_40":1743,"_128":1744,"_130":1745,"_132":1746,"_134":-5,"_13":-5,"_120":1747,"_122":136,"_25":1748,"_138":-5,"_139":1749,"_141":1750},"View your Activity Hub and filter exports | GrowthLoop Docs","view-your-activity-hub-and-filter-exports-growthloop-docs","https://docs.growthloop.com/docs/activity-hub","# View your Activity Hub and filter exports\n\n## Export Activity Hub\n\nLearn how to view your Activity Hub in GrowthLoop\n\nIn this article, you'll learn how to view and use your Activity Hub in GrowthLoop. The Activity Hub gives you complete visibility into every export sync being orchestrated from the GrowthLoop platform to destination in a single location.\n\n1. Navigate to \"Activity\" under \"Admin\" section of left menu rail\n2. By default, you will see the most recent exports in your Activity table.\n\n![](https://files.readme.io/fc22d35-Screenshot_2024-01-23_at_8.23.32_PM.png)\n\n2. Filter to exports to specific Destinations\n\n![](https://files.readme.io/f5e5a99-Screenshot_2024-01-23_at_8.23.41_PM.png)\n\n3. Filter to exports with specific Export State\n\n![](https://files.readme.io/8e51118-Screenshot_2024-01-23_at_8.23.53_PM.png)\n\n4. Filter to exports for specific Audiences\n\n![](https://files.readme.io/c8fcf98-audience_activities.png)\n\nIf you experience any issues or have any questions, please reach out to us at [support@growthloop.com](mailto:support@growthloop.com), and we’ll be in touch shortly!\n\nUpdated 5 months ago\n\n* * *\n\n* [Manage Teams](https://docs.growthloop.com/docs/manage-teams)","2024-03-20T21:02:31.716Z","321c709b-bb1b-4296-a378-2940af0e6e51",[],[],{"_40":1752,"_128":1753,"_130":1754,"_132":1755,"_134":-5,"_13":-5,"_120":1756,"_122":136,"_25":1757,"_138":-5,"_139":1758,"_141":1759},"Why and how to set up Models | GrowthLoop Docs","why-and-how-to-set-up-models-growthloop-docs","https://docs.growthloop.com/docs/models","# Why and how to set up Models\n\nCustomize datasets for audience building without altering your underlying data architecture.\n\nHere at GrowthLoop, our goal is to empower you to maximize the value of your data warehouse by building audiences and activating them across sales and marketing channels. This may sometimes require your analytics team to quickly manipulate underlying datasets to better support customer segmentation. That’s why we’re introducing **GrowthLoop Models** as a way for analysts to create custom data models for audience building - without altering your underlying data architecture.\n\nGrowthLoop Models allows you to curate new data assets quickly and flexibly from within the GrowthLoop platform. Use this feature to:\n\n* Join tables to enrich datasets with new columns\n* Materialize commonly-used calculated fields like total purchase count last 7 days or lifetime spend\n* Alias columns with business-friendly labels\n* Perform rules-based customer exclusion\n* Narrow down large datasets to the most relevant columns\n\nThese data models are stored as views in your data warehouse and surface as datasets for audience segmentation in the GrowthLoop app.\n\n1. Navigate to the **Models** tab on the left side of the GrowthLoop app.\n\n![](https://files.readme.io/c170d4d-models_navigation.png)\n\n‍\n\n2. Click **Create Model**.\n3. Provide a name for your model and decide whether you want the model **Enabled or Disabled.**\n 1. **Enabled:** Your model will become immediately available as a dataset for audience segmentation.\n 2. **Disabled:** Your model will be kept in “draft mode” and will not be available as a dataset. You can come back and **Enable** the model at another time.\n\n![](https://files.readme.io/6dd2626-model_name.png)\n\n4. Write a SQL query to describe the structure of your new data model. Common use cases include:\n 1. Using a WHERE clause to limit values pulled into the view\n 2. Limiting your SELECT clause to a subset of relevant fields\n 3. Aliasing columns to provide business users with more intuitive field names\n 4. Joining in additional tables to enrich the data available within the view\n\n![model sql input](https://files.readme.io/c7a14d2-model_sql_input.png)\n\nThis example query selects a subset of fields (customer\\_id, email, city, and state) from a table of customer data. It aliases the email column to email\\_address and limits the values in the table to customer records from New York.\n\n5. Click **Preview Model** on the bottom right. This will generate a preview of the new data model below the query builder. You can continue to modify your query and refresh the preview until you are satisfied with the structure of the data model.\n\n![](https://files.readme.io/022c976-preview_model.png)\n\n‍\n\n6. Once satisfied with the new data model, click **Save Model.** This data model will be generated as a view inside the **GrowthLoop\\_system** schema in your data warehouse. It will also appear as a data model on your **Models** page within the GrowthLoop app.\n\n![](https://files.readme.io/906696b-save_model.png) ![](https://files.readme.io/6f4b843-list_models.png)\n\nYou can check for this new view in **GrowthLoop\\_system.** It will appear as **\"model\\_\"**:\n\n‍\n\n7. You are now able to connect your custom view to GrowthLoop to perform audience segmentation. In the GrowthLoop platform, click **Datasets,** then **New Dataset.**\n\n![](https://files.readme.io/87991f8-new_dataset.png)\n\n8. Choose your **Dataset Type** and then locate your view by selecting the correct **Dataset** and **Table** from the dropdowns below. You can alias your model in the app with a different name if desired.\n\n![](https://files.readme.io/660bc07-dataset_model_setup.png)\n\n9. Identify the **Unique Key** of your model, select the **Default Fields** that will be shown automatically when the model is used for segmentation, and add any **Labels** that match the fields in the model.\n10. Select your desired options for the **Primary Fields** section (note that this is for the **Users** dataset type - if you selected a different dataset type, you will be asked instead for the fields used to join this model to your Users table). Click **Save.**\n\n* * *\n\nYour model is now available to use for segmentation in the GrowthLoop Audience Builder!\n\nExperiencing any issues with GrowthLoop Models? Reach out to us at **[support@growthloop.com](mailto:support@growthloop.com)** and we’ll be in touch shortly!\n\nUpdated 5 months ago\n\n* * *","2024-03-20T21:02:23.626Z","bf3aa91f-b46d-426f-9a79-263e820d8967",[],[],"collections",[],"uncategorizedArticles",[1764,1767,1770,1773,1776,1779,1782,1785,1788,1791,1794,1797,1800,1803,1806,1809,1812,1815,1818,1821,1824,1827,1830,1833,1836,1839,1842,1845,1848,1851,1854,1857,1860,1863,1866,1869,1872,1875,1878,1881,1884,1887,1890,1893,1896,1899,1902,1905,1908,1911,1914],{"_40":127,"_128":129,"_130":131,"_132":133,"_134":-5,"_13":-5,"_120":135,"_122":136,"_25":137,"_138":-5,"_139":1765,"_141":1766},[],[],{"_40":127,"_128":144,"_130":145,"_132":146,"_134":-5,"_13":-5,"_120":147,"_122":136,"_25":148,"_138":-5,"_139":1768,"_141":1769},[],[],{"_40":127,"_128":152,"_130":153,"_132":146,"_134":-5,"_13":-5,"_120":154,"_122":136,"_25":155,"_138":-5,"_139":1771,"_141":1772},[],[],{"_40":159,"_128":160,"_130":161,"_132":162,"_134":-5,"_13":-5,"_120":163,"_122":136,"_25":164,"_138":-5,"_139":1774,"_141":1775},[],[],{"_40":168,"_128":169,"_130":170,"_132":171,"_134":-5,"_13":-5,"_120":172,"_122":136,"_25":173,"_138":-5,"_139":1777,"_141":1778},[],[],{"_40":177,"_128":178,"_130":179,"_132":180,"_134":-5,"_13":-5,"_120":181,"_122":136,"_25":182,"_138":-5,"_139":1780,"_141":1781},[],[],{"_40":186,"_128":187,"_130":188,"_132":189,"_134":-5,"_13":-5,"_120":190,"_122":136,"_25":191,"_138":-5,"_139":1783,"_141":1784},[],[],{"_40":195,"_128":196,"_130":197,"_132":198,"_134":-5,"_13":-5,"_120":199,"_122":136,"_25":200,"_138":-5,"_139":1786,"_141":1787},[],[],{"_40":204,"_128":205,"_130":206,"_132":207,"_134":-5,"_13":-5,"_120":208,"_122":136,"_25":209,"_138":-5,"_139":1789,"_141":1790},[],[],{"_40":213,"_128":214,"_130":215,"_132":216,"_134":-5,"_13":-5,"_120":217,"_122":136,"_25":218,"_138":-5,"_139":1792,"_141":1793},[],[],{"_40":222,"_128":223,"_130":224,"_132":225,"_134":-5,"_13":-5,"_120":226,"_122":136,"_25":227,"_138":-5,"_139":1795,"_141":1796},[],[],{"_40":231,"_128":232,"_130":233,"_132":234,"_134":-5,"_13":-5,"_120":235,"_122":136,"_25":236,"_138":-5,"_139":1798,"_141":1799},[],[],{"_40":240,"_128":241,"_130":242,"_132":243,"_134":-5,"_13":-5,"_120":244,"_122":136,"_25":245,"_138":-5,"_139":1801,"_141":1802},[],[],{"_40":249,"_128":250,"_130":251,"_132":252,"_134":-5,"_13":-5,"_120":253,"_122":136,"_25":254,"_138":-5,"_139":1804,"_141":1805},[],[],{"_40":258,"_128":259,"_130":260,"_132":261,"_134":-5,"_13":-5,"_120":262,"_122":136,"_25":263,"_138":-5,"_139":1807,"_141":1808},[],[],{"_40":267,"_128":268,"_130":269,"_132":270,"_134":-5,"_13":-5,"_120":271,"_122":136,"_25":272,"_138":-5,"_139":1810,"_141":1811},[],[],{"_40":276,"_128":277,"_130":278,"_132":279,"_134":-5,"_13":-5,"_120":280,"_122":136,"_25":281,"_138":-5,"_139":1813,"_141":1814},[],[],{"_40":285,"_128":286,"_130":287,"_132":288,"_134":-5,"_13":-5,"_120":289,"_122":136,"_25":290,"_138":-5,"_139":1816,"_141":1817},[],[],{"_40":294,"_128":295,"_130":296,"_132":297,"_134":-5,"_13":-5,"_120":298,"_122":136,"_25":299,"_138":-5,"_139":1819,"_141":1820},[],[],{"_40":303,"_128":304,"_130":305,"_132":306,"_134":-5,"_13":-5,"_120":307,"_122":136,"_25":308,"_138":-5,"_139":1822,"_141":1823},[],[],{"_40":312,"_128":313,"_130":314,"_132":315,"_134":-5,"_13":-5,"_120":316,"_122":136,"_25":317,"_138":-5,"_139":1825,"_141":1826},[],[],{"_40":321,"_128":322,"_130":323,"_132":324,"_134":-5,"_13":-5,"_120":325,"_122":136,"_25":326,"_138":-5,"_139":1828,"_141":1829},[],[],{"_40":330,"_128":331,"_130":332,"_132":333,"_134":-5,"_13":-5,"_120":334,"_122":136,"_25":335,"_138":-5,"_139":1831,"_141":1832},[],[],{"_40":339,"_128":340,"_130":341,"_132":342,"_134":-5,"_13":-5,"_120":343,"_122":136,"_25":344,"_138":-5,"_139":1834,"_141":1835},[],[],{"_40":348,"_128":349,"_130":350,"_132":351,"_134":-5,"_13":-5,"_120":352,"_122":136,"_25":353,"_138":-5,"_139":1837,"_141":1838},[],[],{"_40":357,"_128":358,"_130":359,"_132":360,"_134":-5,"_13":-5,"_120":361,"_122":136,"_25":362,"_138":-5,"_139":1840,"_141":1841},[],[],{"_40":366,"_128":367,"_130":368,"_132":369,"_134":-5,"_13":-5,"_120":370,"_122":371,"_25":372,"_138":-5,"_139":1843,"_141":1844},[],[],{"_40":376,"_128":377,"_130":378,"_132":379,"_134":-5,"_13":-5,"_120":380,"_122":136,"_25":381,"_138":-5,"_139":1846,"_141":1847},[],[],{"_40":385,"_128":386,"_130":387,"_132":388,"_134":-5,"_13":-5,"_120":389,"_122":136,"_25":390,"_138":-5,"_139":1849,"_141":1850},[],[],{"_40":394,"_128":395,"_130":396,"_132":397,"_134":-5,"_13":-5,"_120":398,"_122":136,"_25":399,"_138":-5,"_139":1852,"_141":1853},[],[],{"_40":403,"_128":404,"_130":405,"_132":406,"_134":-5,"_13":-5,"_120":407,"_122":136,"_25":408,"_138":-5,"_139":1855,"_141":1856},[],[],{"_40":412,"_128":413,"_130":414,"_132":415,"_134":-5,"_13":-5,"_120":416,"_122":136,"_25":417,"_138":-5,"_139":1858,"_141":1859},[],[],{"_40":421,"_128":422,"_130":423,"_132":424,"_134":-5,"_13":-5,"_120":425,"_122":136,"_25":426,"_138":-5,"_139":1861,"_141":1862},[],[],{"_40":430,"_128":431,"_130":432,"_132":433,"_134":-5,"_13":-5,"_120":434,"_122":136,"_25":435,"_138":-5,"_139":1864,"_141":1865},[],[],{"_40":439,"_128":440,"_130":441,"_132":442,"_134":-5,"_13":-5,"_120":443,"_122":136,"_25":444,"_138":-5,"_139":1867,"_141":1868},[],[],{"_40":448,"_128":449,"_130":450,"_132":451,"_134":-5,"_13":-5,"_120":452,"_122":136,"_25":453,"_138":-5,"_139":1870,"_141":1871},[],[],{"_40":457,"_128":458,"_130":459,"_132":460,"_134":-5,"_13":-5,"_120":461,"_122":136,"_25":462,"_138":-5,"_139":1873,"_141":1874},[],[],{"_40":466,"_128":467,"_130":468,"_132":469,"_134":-5,"_13":-5,"_120":470,"_122":136,"_25":471,"_138":-5,"_139":1876,"_141":1877},[],[],{"_40":475,"_128":476,"_130":477,"_132":478,"_134":-5,"_13":-5,"_120":479,"_122":136,"_25":480,"_138":-5,"_139":1879,"_141":1880},[],[],{"_40":484,"_128":485,"_130":486,"_132":487,"_134":-5,"_13":-5,"_120":488,"_122":136,"_25":489,"_138":-5,"_139":1882,"_141":1883},[],[],{"_40":493,"_128":494,"_130":495,"_132":496,"_134":-5,"_13":-5,"_120":497,"_122":136,"_25":498,"_138":-5,"_139":1885,"_141":1886},[],[],{"_40":502,"_128":503,"_130":504,"_132":505,"_134":-5,"_13":-5,"_120":506,"_122":136,"_25":507,"_138":-5,"_139":1888,"_141":1889},[],[],{"_40":511,"_128":512,"_130":513,"_132":514,"_134":-5,"_13":-5,"_120":515,"_122":136,"_25":516,"_138":-5,"_139":1891,"_141":1892},[],[],{"_40":520,"_128":521,"_130":522,"_132":523,"_134":-5,"_13":-5,"_120":524,"_122":136,"_25":525,"_138":-5,"_139":1894,"_141":1895},[],[],{"_40":529,"_128":530,"_130":531,"_132":532,"_134":-5,"_13":-5,"_120":533,"_122":136,"_25":534,"_138":-5,"_139":1897,"_141":1898},[],[],{"_40":538,"_128":539,"_130":540,"_132":541,"_134":-5,"_13":-5,"_120":542,"_122":136,"_25":543,"_138":-5,"_139":1900,"_141":1901},[],[],{"_40":547,"_128":548,"_130":549,"_132":550,"_134":-5,"_13":-5,"_120":551,"_122":136,"_25":552,"_138":-5,"_139":1903,"_141":1904},[],[],{"_40":556,"_128":557,"_130":558,"_132":559,"_134":-5,"_13":-5,"_120":560,"_122":136,"_25":561,"_138":-5,"_139":1906,"_141":1907},[],[],{"_40":565,"_128":566,"_130":567,"_132":568,"_134":-5,"_13":-5,"_120":569,"_122":136,"_25":570,"_138":-5,"_139":1909,"_141":1910},[],[],{"_40":574,"_128":575,"_130":576,"_132":577,"_134":-5,"_13":-5,"_120":578,"_122":136,"_25":579,"_138":-5,"_139":1912,"_141":1913},[],[],{"_40":583,"_128":584,"_130":585,"_132":586,"_134":-5,"_13":-5,"_120":587,"_122":136,"_25":588,"_138":-5,"_139":1915,"_141":1916},[],[],"mixpanelToken","cc23843c498db1553f595eae3fae57d7","sentryDsn","https://cd638f7e7e056e6e02d1d91f09ba2fa9@o563911.ingest.us.sentry.io/4510302612946944","environment","prd","theme","isMac","docs-content",{"_66":1927,"_1927":1928,"_1931":1932,"_1937":1938,"_1939":1940,"_1941":1942},"article",{"_40":1113,"_128":1114,"_130":1115,"_132":1116,"_134":-5,"_13":-5,"_120":1117,"_122":136,"_25":1118,"_138":-5,"_139":1929,"_141":1930},[],[],"breadcrumbData",{"_1933":1934,"_1935":1936},"currentItem",{"_25":1114,"_75":1113,"_66":1927},"breadcrumbs",[],"prevArticle",{"_25":1109,"_40":1104,"_128":1105},"nextArticle",{"_25":1127,"_40":1122,"_128":1123},"context",{"_23":24},"actionData","errors"]