This article describes how to set up the Google Cloud Pub/Sub (Service Account) connector.

In this article:

Prerequisites

Google Cloud – Web Application Credentials

For this connector to work correctly you must update to Google Cloud web application Restrictions settings to whitelist Tealium servers and provide the required callback upon successful connection.

From the Google Cloud console, go to Credentials and edit the Restrictions sections with the following values, as indicated in the example that follows.

Connector Actions

Action Name AudienceStream EventStream
Send Event Data to Topic
Send Visitor Data to Topic
Send Customized Data to Topic (Advanced)

Configure Settings

Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector.

After adding the connector, configure the following settings:

  • Google Cloud Platform Project ID
    • Required
    • Enter the Project ID.
  • Client Email
    • Required
    • Enter the client email with access to the Pub/Sub API.
    • To generate service-account credentials or view the public credentials already generated, navigate to the Credentials Page
    • For additional information, see Creating a service account.
  • Private Key
    • Required
    • Enter the private key of the client.
    • You can obtain this key by navigating to the Credentials Page.

Action Settings - Parameters and Options

Click Next or go to the Actions tab. This is where you configure connector actions.

This section describes how to set up parameters and options for each action.

Action - Send Event Data to Topic

Parameters

Parameter Description
Project Topic
  • Required
  • Select the topic in your Pub/Sub project to publish the message to.
Message Attributes
  • Optional
  • Map your attribute values to custom Pub/Sub message attributes.
  • Enter the message attribute key in the To drop-down list.
Print Attribute Names
  • If attribute names are updated, the names in the payload automatically reflect the updated name in the published message.

Action - Send Visitor Data to Topic

Parameters

Parameter Description
Project Topic
  • Required
  • Select the topic in your Pub/Sub project to publish the message to.
Message Attributes
  • Optional
  • Map your attribute values to custom Pub/Sub message attributes.
  • Enter the message attribute key in the To drop-down list.
Include Current Visit Data
  • Checking this box will include both visitor data and current visit data in the published message.
Print Attribute Names
  • If attribute names are updated, the names in the payload automatically reflect the updated name in the published message.

Action - Send Customized Data to Topic (Advanced)

Parameters

Parameter Description
Project Topic
  • Required
  • Select the topic in your Pub/Sub project to publish the message to.
Message Attributes
  • Optional
  • Map your attribute values to custom Pub/Sub message attributes.
  • Enter the message attribute key in the To drop-down list.
Custom Message Definition
  • Required
  • Provide values to construct message data.
  • For template support, reference the template name to generate message data from the template.
  • Map values to names for simple one-level JSON format, otherwise reference the template name and select only the Custom Message Definition option.
Template Variables
  • Optional
  • Provide template variables as data input for templates.
  • For additional information, see the Template Variables Guide.
  • Name nested template variables with the dot notation.
  • Example: items.name
  • Nested template variables are typically built from data layer list attributes.
Templates
  • Optional
  • Provide templates to be referenced in either message attributes or data.
  • For more information, see the Templates Guide.
  • Templates are injected by name with double curly braces into supported fields.
  • Example: {{SomeTemplateName}}

Vendor Documentation

Public