Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BD-3368 Add catalog views details #7905

Merged
merged 1 commit into from
Aug 15, 2024
Merged

BD-3368 Add catalog views details #7905

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion _docs/_user_guide/data_and_analytics/cloud_ingestion/sync_catalogs_data.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -173,7 +173,9 @@ CREATE TABLE `BRAZE-CLOUD-PRODUCTION.INGESTION.CATALOGS_SYNC`

## How the integration works

Each time the sync runs, Braze will pull in all rows where `UPDATED_AT` is after the last timestamp synced. We recommend creating a view from your catalog data to set up a source table that will fully refresh each time a sync runs. For example, if you have a table of product data (`product_catalog_1`) with `product_id` and three additional attributes, you could sync the below view:
Each time the sync runs, Braze will pull in all rows where `UPDATED_AT` is after the last timestamp synced. We recommend creating a view in your data warehouse from your catalog data to set up a source table that will fully refresh each time a sync runs. With views, you won't need to rewrite the query each time.

For example, if you have a table of product data (`product_catalog_1`) with `product_id` and three additional attributes, you could sync the below view:

{% tabs %}
{% tab Snowflake %}
Expand Down