Skip to main content

What this destination does

Google Pub/Sub is a destination: it sends data out of Zeotap CDP into a Google Cloud Pub/Sub topic that you own, in real time, as users move through a Journeys workflow. Zeotap CDP is the publisher on that topic; your own systems consume the messages from it. Google Pub/Sub itself is an asynchronous and scalable messaging service that decouples the services producing messages from the services processing them. It is commonly used for streaming analytics and data integration pipelines that ingest and distribute data. Pub/Sub also exists in Zeotap CDP in the opposite direction, as a source that brings data into the platform. If that is what you need, use one of these instead:
  • Pub/Sub Stream — ingest messages into Zeotap CDP as they are published.
  • Pub/Sub Batch — ingest messages into Zeotap CDP in batches.
The source and the destination are configured separately and share no settings. This page covers the destination only.

Prerequisites

Ensure that you have the following details available before starting the integration:
  • Project ID — the Google Cloud project that owns the topic. See Project ID.
  • Topic ID — the Pub/Sub topic you want Zeotap CDP to publish to. See Topic ID.
  • Authentication — either a Refresh Token (Client ID, Client Secret, and Refresh Token) or a Service Account. See Authentication.
  • A Journeys workflow, or the ability to create one — the destination is created and attached from inside a workflow. See Create a Workflow.

Supported identifiers and actions

Use + Add Mapping Field on the mapping screen to add any custom field you want to send to Google Pub/Sub.

Gather your Google Cloud details

Project ID

A Project ID is a unique string that differentiates your project from all others on Google Cloud. You can use the Google Cloud console to generate a Project ID. You can find the Project ID in the Google Cloud console — Dashboard page. In the example below, the Project name is My Sample Project and the Project ID is my-sample-project-191923.
The Google Cloud console Dashboard showing the Project name and Project ID

Topic ID

In the Google Cloud console, go to the Pub/Sub page → Topics. A list of all the topics created appears. Copy the relevant Topic ID and use it for the destination setup.
The Topics list on the Pub/Sub page of the Google Cloud console

Authentication

The authentication method for the Pub/Sub destination can be Refresh Token or Service Account. Provide the required details based on the authentication method you choose.

Refresh token authentication

To authenticate using a Refresh Token, you need the following details:
  • Client ID
  • Client Secret
  • Refresh Token
For this integration, if you decide to perform the authentication through the Refresh Token, then Zeotap CDP requires the Client ID, Client Secret, and Refresh Token to establish a connection with the Pub/Sub destination where you want to send data. In Google Cloud, these unique credentials can be used to authorise applications or services, such as Pub/Sub, through OAuth 2.0. For detailed steps to generate them, refer to Google’s OAuth playground documentation. In the refresh token generation steps, add the Cloud Pub/Sub API v1 scope when specifying API scopes, as shown in the image below.
Selecting the Cloud Pub/Sub API v1 scope while specifying API scopes

Service account authentication

To authenticate using a Service Account, you must assign the Pub/Sub Publisher role to the pub-sub-publisher@dcr-orchestration-prod.iam.gserviceaccount.com service account within Pub/Sub, as shown below.
Assigning the Pub/Sub Publisher role to the Zeotap service account in Google Cloud

Create the destination

This page covers creating the Google Pub/Sub destination from inside a Journeys workflow. Once you have taken care of the prerequisites above, create the workflow in Journeys (Zeotap CDP). After you have applied filters or added conditions for your users in Journeys as described in Create a Workflow, you can activate them in Google Pub/Sub from the Send to Destinations node, as shown below.
The Send to Destinations node in a Journeys workflow
A new window appears, where you can set up your destination. You can use an already existing destination from the list of available Destinations, or create a new one by clicking + Add New Destination.
Choosing an existing destination or adding a new one in the Send to Destinations window
To use an existing destination for activation in Journeys, go to Link the destination in a Journeys workflow.
Perform the following steps to add a new destination:
1
Click + Add New Destination.
2
Search for Google Pub/Sub.
3
Click Google Pub/Sub and enter a name for the Destination.
4
Enter the Instance, which is an internal field for the Destination.
5
Provide the Project Id and Topic Id obtained from your Google Cloud. See Project ID and Topic ID.
Entering the Instance, Project Id, and Topic Id on the destination form
6
Choose either Refresh Token or Service Account as your Authentication method, based on your requirement.a. If you choose Refresh Token, provide the Client Id, Client Secret, and Refresh Token details in the respective fields. See Refresh token authentication.
Refresh Token authentication fields on the destination form
b. If you choose Service Account, the following Google Service Account is displayed. Ensure that you grant the Pub/Sub Publisher role to this service account within Pub/Sub. See Service account authentication.Service Account: pub-sub-publisher@dcr-orchestration-prod.iam.gserviceaccount.com
The Google Service Account displayed when Service Account authentication is selected
7
In the mapping screen that appears, under Choose your Action, select Send identifiers to Google Cloud PubSub in realtime as the action for sending data from the workflow created in Journeys.Under Map the Fields, use + Add Mapping Field to add any custom field that you wish to send to Google Pub/Sub. Ensure that you map at least one attribute. Otherwise, the data does not flow to the Pub/Sub destination.
Choosing the action and mapping fields for the Pub/Sub destination
8
Once the mapping is complete, click Create Destination. The destination is created and made available for activation on Journeys, as shown below.
The created Pub/Sub destination available for activation in Journeys
After creating a destination, link it in the Send to Destinations node within the workflow, as explained below.
1
In the workflow, click + and choose Send to Destinations.
Adding a Send to Destinations node to a Journeys workflow
2
Choose the destination from the list of available destinations by using the search feature.
3
Under the Destination Details tab, based on the authentication type you have chosen, the Instance, Project Id, Topic Id, Authentication (Refresh Token/Service Account) and other fields shown in the image below populate automatically from the values you entered while creating the destination. However, you need to provide an Audience Name to save the Destination.
The Destination Details tab with auto-populated fields and the Audience Name field
4
Under the Destination Settings tab, choose the action and mapping as per your requirement.
The Destination Settings tab showing the action and field mapping
5
Click Save Destination. The destination is attached, as shown in the image below.
The Pub/Sub destination attached to the workflow
6
Click Add Destinations at the bottom right corner of the screen. You can also add multiple destinations at this step if needed.
7
The linked Destinations appear in the Send to Destinations node within the workflow, as shown below. You can then build and customise your workflow as needed by clicking +. Note that you must enter a name for your workflow in the provided text box to save it.
Linked destinations shown inside the Send to Destinations node
8
After adding conditions and filters for users, choose one of the following options:
  • Save Draft — enables you to revisit and edit the workflow before publishing.
  • Next: Re-entry Condition — determines whether a user can re-enter the same workflow.
9
After defining the re-entry criteria, click Publish Workflow. The workflow appears in the Workflow listing screen with a Published status.
The journey re-entry conditions panel, with the Publish Workflow button

Verify the destination is delivering

After publishing the workflow, confirm delivery end to end:
  1. In the workflow, the Google Pub/Sub destination appears inside the Send to Destinations node.
  2. On the Workflow listing screen, the workflow shows a Published status. A workflow left in draft does not deliver.
  3. On the destination, at least one attribute is mapped under Map the Fields. With no mapped attribute, no data flows to the topic.
  4. In the Google Cloud console, open Pub/Sub → Topics and select the topic named by your Topic Id. Confirm that messages are being published to it as users flow through the journey.

Troubleshooting

FAQ

This page describes the destination — Zeotap CDP publishes data out to a Pub/Sub topic that you own, from a Journeys workflow. Pub/Sub also exists as a source that brings data into Zeotap CDP; see Pub/Sub Stream and Pub/Sub Batch. The source and the destination are configured separately and do not share settings.
Both are supported; choose the one that fits your requirement. Refresh Token needs a Client ID, Client Secret, and Refresh Token generated with the Cloud Pub/Sub API v1 scope. Service Account needs no credentials from you — instead, you grant the Pub/Sub Publisher role to the Google Service Account shown on the destination form.
Yes. Map at least one attribute under Map the Fields. If no attribute is mapped, data does not flow to the Pub/Sub destination. Use + Add Mapping Field to add custom fields.
Yes. In the Send to Destinations node, click Add Destinations to attach additional destinations to the same workflow.
Yes. A destination is configured once and reused across audiences and journeys — see Destinations. Select it from the list of available destinations in the Send to Destinations node of any workflow, and provide an Audience Name for that workflow.

Next steps

Last modified on November 5, 2026