Create a recipe in Data Connect

To enable Data Connect and begin creating and managing recipes, contact your Tealium Customer Success Manager.

Complete the following steps to create a recipe:

1. Navigate to DataConnect > Integrations.

2. In the Integrations screen, click Create > Recipe.

3. In the My new recipe slideout, enter a name for the recipe and select the profile associated with the recipe.

4. Under Pick a starting point, select how you want to trigger your app in Workato.

   • Select Run on a schedule to build a recipe that runs on a schedule for your business case.
   • Select Trigger from an App to build a recipe that periodically polls the source system for new data.

     For more information about Workato triggers, see the Triggers article in the Workato Recipe Components documentation. To see which triggers are available for your app, read the app-specific document in the Pre-built Connectors documentation.

5. Click Start building.

Build a recipe

Now you can start building your recipe in Workato. Generally, your recipes will follow a specific workflow:

1. Select a trigger.
2. Configure an action.
3. Configure error handling.

Step 1: Select a trigger

App-based triggers
Search for the app you want to integrate into Tealium. For schedule-based recipes, the trigger is the schedule that you configure.

1. In the Trigger step, choose the trigger for your business case.

   Use batch processing when available to reduce the number of tasks per recipe.

2. In the Connection step, connect to your app. Enter a connection name and complete the configuration. Click Connect.

3. In the Setup step, add any additional configurations for this app trigger. Set a trigger condition if you want to set a more specific trigger.

Step 2: Configure an action

1. Under Actions click +.
2. Under What happens next? select Handle errors.
   We recommend wrapping the Tealium Events app and related actions in an error monitoring step.
3. Select any apps you need to prepare the data to be imported to Tealium. For example, use the Download file contents in Amazon S3, Decrypt and verify data, and Parse CSV apps together to prepare encrypted CSV data stored in an Amazon S3 bucket.
4. You must use the Repeat action loop with the Tealium Events app.
   1. Click the + to see a list of actions.
   2. Click Repeat action.
   3. Set the loop Repeat mode to Batch of items.
   4. Set the Batch size to the maximum batch size for your app.
5. Under Select an app and action, select the Tealium Events app.
6. Click Show optional fields, and ensure all available fields are selected. Configure each field as needed for your use case.

   • Attribute mappings - Configure attribute mappings. If you do not map attributes, they will be sent to Tealium using the attribute names from your source data. Use this feature to edit key names to match existing Tealium configurations to minimize additional work for new attributes, enrichments, and/or rules.

     We recommend that you map attributes first so that you can use the appropriate mapped attribute names in the rest of the app configuration.

   • Source Attribute Name - Use the Text option and enter the API names of the data points you want to rename.

   • Tealium Attribute Name - Use the Text option and enter the desired event attribute name.

     Event attribute names can contain only letters, numbers, underscores, dollar signs, square brackets, and periods. Spaces are not allowed.

   • Encode Visitor ID - Determines whether the visitor ID is encoded with SHA-256. The default value is No.

     Encode Visitor ID is applied only if Visitor Attribute ID is defined.

   • Attributes to remove - A comma-separated list of the API names of any attributes that should be removed. Use this option to remove sensitive or unnecessary attributes from the Tealium event.

   • Attributes to add - Specify the key and value to be added. For the key, use the Text input to type the desired attribute name. For the value, use the Text input to hardcode a value or use the Formula input to edit or create a value from a datapill.

     We recommend using this feature to hardcode a tealium_event value to create an event specification.

   • Fields Separator - Set a fields separator when the visitor ID value is nested inside an object. The default separator is a vertical bar |. You can change the default value by using the Text option and typing in the separator for your use case.

7. Configure the Tealium Events app using the information from your Tealium Connect data source.

   1. Under Tealium API Domain, enter your regional Tealium API domain.

   2. Enter your Data Source Key from your Tealium Collect data source.

   3. Enter your Tealium account name and profile name.

      A single account may have multiple corresponding profiles. Specify the Tealium profile connected to this recipe.

   4. In the Source Data field, select the datapill to populate the field with data to send to Tealium. When sending batched data to Tealium, click Formula input and select Batched from the Recipe data slideout.

      Ensure your Source Data contains fields with unique names, ignoring case. Workato apps do not guarantee successful parsing of fields with matching names in different cases. For example, field_name and Field_name may cause an error during parsing.
      Tealium processes all event field names in lowercase.

   5. Select a datapill for the Visitor ID Value or, if you mapped attributes previously, use the Tealium Attribute Name from your data mapping. This value directly sets the tealium_visitor_id.

   6. Enter a value for the corresponding Visitor Attribute ID found in your Tealium account.
      Navigate to AudienceStream > Visitor/Visit Attributes, select the visitor attribute you want to use, and copy the attribute ID to your Tealium Events app in Workato.

   7. (Optional) Add any additional attributes you want to send to Tealium that are not necessarily from your app. For example, tealium_event, your tealium_trace_id, or _dc_ttl_, which describes how long the visit will last.

Step 3: Configure error handling

1. Click the On Error step.
2. Under Retry actions in Monitor block?, choose whether to retry actions.
3. Create an email notification.
   1. Select an app to trigger when an error occurs. For example, you can send an email with error information using the Email by Workato app.
   2. Configure the app with your contact information.
   3. From the Recipe data slideout, select datapills with information about the error monitoring to include in your email message.
4. Add a log message to the job report.
   1. Click the + to add an additional action to fire when an error occurs.
   2. Click Action in an app and select the Logger by Workato app.
   3. Configure the message for the logs.
5. Stop the recipe.
   1. Click the + to add an additional action when an error occurs.
   2. Click Action in an app and select the ReceipeOps by Workato app.
   3. Select the Stop a recipe action.
   4. Under Whose account are you managing?, select My account.
   5. Click Connect.
   6. In the Setup step, select the current recipe name from the Recipe drop down list.
   7. Select Yes from the Force stop drop-down list.
6. Stop the current job.
   1. Click the final + in your recipe to add an additional action when the error occurs.
   2. Click Stop job.
   3. Under In job report, mark stopped job as, select Failed in the drop down list.
   4. Under Reason for failure, type Error.
7. Click Save.
8. Click Test to test your recipe configuration.