RudderStack Docs – Management, Scheduling, and Data Activation

Archive: Import Profiles Project from Git

Mon, 01 Jan 0001 00:00:00 +0000

You can import a Profiles project created using the Profile Builder (PB) tool and stored in a Git repo to:

View the project, its details, and the output tables in the UI.
Schedule the Profiles project to run at the specified frequency and time interval.
Seamlessly collaborate with your teammates, with modular control over your model files.

Prerequisites

Profiles project in a Git repository.

RudderStack recommends using a different target schema and user for Profiles for RudderStack app than the one used for CLI project. This will maintain differentiation in case of manual runs (using CLI) and scheduled runs (using RudderStack app):

Steps

To import the Profiles project from a Git repository into the RudderStack platform:

Log in to the RudderStack app and go to Unify > Profiles from the left sidebar.
Click Create project.

Select Import project from Git Repo on the next screen.
Enter a name and description for your Profiles project.
Enter the SSH URL of your Git repository to be used for your Profiles project:

You cannot edit this Git repository URL later.

Note that:

The SSH URL you provide must contain the Profiles project, otherwise it will cause an error.

The git SSH URL must match one of the below patterns:

git@<provider-host>:<org-name>/<repo-name>/tree/<branch-name>

git@<provider-host>:<org-name>/<repo-name>

git@<provider-host>:<org-name>/<repo-name>/tree/main/path/to/project

ssh://git@host:port/path.git

RudderStack supports any subfolder in the git project without the .git extension.

See the respective documentation for more information:

GitHub

GitLab

BitBucket

Azure DevOps

Copy the SSH public key. Then, click Add deploy key which will take you to your git repository’s Deploy keys section. See Set up deploy keys for more information.

Click Add deploy key. Then, add a Title, paste your SSH public key, and click Add key.
Go back to the RudderStack app, then click Continue to let RudderStack verify read access.
Select the warehouse and enter its credentials to store this Profiles project.

Click Create Profiles project.

Then, you can choose any of the following options:

View Profiles project which takes you to the Overview tab of the project to view project details.
Run Profiles project which takes you to the History tab of the project from where you can click Run to run the project.

You can also explore other project settings in the different tabs.

Once you import a git project, you cannot edit the Git repository URL.

Fetch latest project changes

RudderStack caches your imported project details (like the number of features) to power the RudderStack dashboard.

If you have recently pushed changes to your Git repository and want to see them reflected in the dashboard immediately, go to the Settings page of your Profiles project and click Fetch latest to refresh the cache.

The Fetch latest button only refreshes the dashboard view. When you trigger a Profiles run — either manually, via a schedule, or through the Profiles API — RudderStack automatically fetches the latest code from your connected Git repository.

Archive: Schedule

Mon, 01 Jan 0001 00:00:00 +0000

Once you have imported your Profiles project from Git repository in the RudderStack app, you can schedule it to run at the specified frequency and time interval.

Go to the Settings tab of your project and click the edit icon in the Schedule info section:

Basic

Use this setting to run syncs at a given time interval and specified time (in UTC).

Frequency - You can choose the data sync frequency from the following options:
- 15 minutes
- 30 minutes
- 1 hour
- 3 hours
- 6 hours
- 12 hours
- 24 hours
Sync Starting At - Specify the time (in UTC) at which the data sync should start.

CRON

Schedule your project using CRON expressions for more specific scheduling, for example, daily on Tuesdays and Thursdays.

Use the CRON scheduler utility to get the CRON expression.

Manual

This setting lets you run the Profiles project manually. RudderStack won’t start the run until you explicitly trigger it by navigating to the History tab of your project and clicking Run.

Archive: Activate Profiles Data

Mon, 01 Jan 0001 00:00:00 +0000

Once you create cohorts and run the project successfully, you can use the Profiles Activations feature to sync your target customer data to the downstream marketing tools like Braze, Mailchimp, etc. This will help you make informed decisions, run personalized marketing campaigns, and enhance the overall customer experience across multiple platforms.

Prerequisites

Import the Profiles project from your Git repository and run it.
For the warehouse used for your Profiles project, you must create the RudderStack schema and grant permissions to it. See the detailed steps for each warehouse:

Add activations

Once you have your Profiles project available in the RudderStack dashboard, you can view the cohorts data after the first successful run.

Follow these steps to add an activation for a cohort:

Click Add activation next to the cohort for which you want to send data to the downstream destination.

Configure the following settings in the Create Activation window:

Setting	Description
Activation name	Assign a name to uniquely identify the activation.
Select identifier	Select the type of ID you want to use for the activation from the dropdown menu.
Select your activation type	Choose a table or audience as your source.

Click Continue to verify your credentials.
Review the details and click Create activation.
Choose from Use existing destination or Set up a new destination to connect your activation to the destination.
Configure the destination-specific settings.
Click Turn on the connection to enable the connection.

You can view your Activations in the list of Sources in the RudderStack dashboard.

View/modify activations

Click [n] Activations next to your cohort:

Click the Activations tab to view the detailed list of all the connected activations:

Click on the activation name. It will take you to the source overview page:

Click the Connection details next to the destination.

Edit the Schema or Settings in the relevant tabs: