Skip to content

Update courier groups and meta events #726

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

Open
jamescott wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Update courier groups and meta events #726

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
7114f19
update paths
jamescott Mar 9, 2026
3ccbe7f
add note about offsets
jamescott Mar 9, 2026
246acf7
edit
jamescott Mar 9, 2026
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: 2 additions & 2 deletions amperity_operator/source/table_transaction_attributes_extended.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,9 +41,9 @@ Transaction Attributes Extended table

.. important:: Many columns in the **Transaction Attributes Extended** table enable specific features within Amperity, such as segment insights, predictive scoring, and churn prevention campaigns.

Any column that exists in the :ref:`column reference <table-transaction-attributes-extended-reference>` must maintain the exact column name and data type, even if your tenant requires custom SQL to enable the feature.
Any column that exists in the **Transaction Attributes Extended** table must maintain the exact column name and data type, even if your tenant requires custom SQL to enable the feature.

The **l12m_order_revenue**, **l12m_order_frequency** and **l12m_total_items** attributes must not be renamed. These attributes populate the **Revenue tree** and **Historical revenue** cards on the segment summary page.
The **l12m_order_revenue**, **l12m_order_frequency** and **l12m_total_items** attributes must not be renamed. These attributes populate the **Revenue tree** and **Historical revenue** cards on the segment summary page and enable segment insights.

This table may be extended to support additional use cases. The implementations for these types of use cases are always tenant-specific, but should follow a similar approach as :ref:`optional <table-transaction-attributes-extended-extend-attributes>` extensions. Custom fields are not used by segment insights and predictive scoring, but may be added to the **Transaction Attributes Extended** table.

Expand Down
14 changes: 9 additions & 5 deletions amperity_reference/source/courier_groups.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,10 +23,12 @@ About courier groups

.. courier-groups-context-start

A courier group is typically configured to run automatically on a recurring schedule. All couriers within a courier group run as a unit. Couriers with required files must complete before any downstream processes, such as Stitch or database generation, can be started.
A courier group, also known as a scheduled workflow, is configured to run automatically on a recurring schedule. All couriers within a courier group run as a unit. Couriers with required files must complete before any downstream processes, such as Stitch or database generation, can be started.

For each courier with required files, Amperity determines if those files have updates, and then pulls updated files to Amperity. Depending on the run type, Amperity may then run Stitch and generate or refresh a customer 360 database. Orchestrations, recurring campaigns, and Profile API indexes may be configured to run as part of a courier group after the customer 360 database is refreshed.

A bridge sync should be in a dedicated courier group.

.. courier-groups-context-end

.. image:: ../../images/mockups-workflow-courier-group-dialog.png
Expand All @@ -39,7 +41,7 @@ For each courier with required files, Amperity determines if those files have up

What a courier group does:

#. Logically organizes a list of couriers and bridges into a group that shares the same schedule and workflow.
#. Logically organizes a list of couriers into a group that shares the same schedule and workflow.
#. Allows for each courier to be assigned schedule variance via wait times and offsets.
#. Enables both automatic and ad hoc runs.
#. Polls each data source associated with a courier in the group to determine if data is ready to be pulled to Amperity.
Expand Down Expand Up @@ -451,7 +453,7 @@ Bridge syncs

.. courier-groups-bridge-syncs-start

Amperity Bridge enables data sharing between Amperity and data lakehouses. Each bridge can be :ref:`configured <courier-groups-howto-add-bridge>` for inbound and outbound shares to give you access to shared tables without replication.
Amperity Bridge enables data sharing between Amperity and data lakehouses. Each bridge can be :ref:`configured <courier-groups-howto-add-bridge>` for inbound and outbound shares to give you access to shared tables without replication. A bridge sync should be in a dedicated courier group.

.. courier-groups-bridge-syncs-end

Expand Down Expand Up @@ -614,7 +616,7 @@ Activate courier group

.. courier-groups-howto-activate-start

An activated courier group is run automatically on a defined schedule. All couriers and bridges that are configured for the courier group run as a unit and are used to run Stitch and refresh the customer 360 database. All orchestrations, orchestration groups, recurring campaigns, and profile API endpoints that are configured for the courier group are run automaticaly after the database is refreshed.
An activated courier group is run automatically on a defined schedule. All couriers configured for the courier group run as a unit refresh domain table data. All orchestrations, orchestration groups, recurring campaigns, and profile API endpoints that are configured for the courier group are run automaticaly after the database is refreshed.

.. courier-groups-howto-activate-end

Expand All @@ -636,7 +638,9 @@ Add bridge to workflow

.. courier-groups-howto-add-bridge-start

Any inbound share that has been configured and activated in your tenant may be added as a bridge within a courier group.
Any inbound share configured and activated in your tenant may be added as a bridge to a scheduled workflow.

.. important:: Add a bridge to a dedicated courier group that runs independently of other scheduled workflows. Assign offsets to courier groups to ensure a scheduled workflow with a bridge sync starts after or ends before other scheduled workflows.

.. courier-groups-howto-add-bridge-end

Expand Down
4 changes: 2 additions & 2 deletions amperity_user/source/events_meta_ads_manager.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,11 +25,11 @@
Send events to Meta Ads Manager
==================================================

.. include:: ../../amperity_user/source/events_meta_ads_manager.rst
.. include:: ../../amperity_operator/source/events_meta_ads_manager.rst
:start-after: .. events-meta-ads-manager-overview-start
:end-before: .. events-meta-ads-manager-overview-end

.. include:: ../../amperity_user/source/events_meta_ads_manager.rst
.. include:: ../../amperity_operator/source/events_meta_ads_manager.rst
:start-after: .. events-meta-ads-manager-overview-window-start
:end-before: .. events-meta-ads-manager-overview-window-end

Expand Down