Skip to content

Sandboxes and very small test audiences #637

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 5 commits into
base: main
Choose a base branch
from
Open

Sandboxes and very small test audiences #637

Show file tree
Hide file tree
Changes from 3 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
e3c9ab3
add best practice for very small test audiences
jamescott Dec 4, 2025
b909bb7
links to sandbox topic and sections
jamescott Dec 4, 2025
7c36eb9
fix path
jamescott Dec 4, 2025
d5e9cf4
add included section to operators guide
jamescott Dec 4, 2025
062c0e4
edit
jamescott Dec 4, 2025
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
15 changes: 14 additions & 1 deletion amperity_reference/source/sandboxes.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -217,6 +217,7 @@ Amperity recommends the following patterns when working with sandboxes:
* :ref:`Delete sandbox on promote <sandboxes-best-practice-delete-on-promote>`
* :ref:`Run partial workflows <sandboxes-best-practice-partial-workflows>`
* :ref:`Short-lived sandboxes <sandboxes-best-practice-short-lived>`
* :ref:`Very small test audiences <sandboxes-best-practice-small-test-audiences>`

.. sandboxes-best-practice-end

Expand Down Expand Up @@ -337,7 +338,7 @@ Run partial workflows

Each workflow should be validated before promoting changes to production using a partial workflow.

* A partial workflow pulls data from upstream sources to the sandbox, run Stitch, and then refresh databases.
* A partial workflow pulls data from upstream sources to the sandbox, runs Stitch, and then refreshes databases.
* A partial workflow *does not* run orchestrations *or* campaigns. This ensures that data in your sandbox is not inadvertently sent to any downstream workflows.

.. sandboxes-best-practice-partial-workflows-end
Expand Down Expand Up @@ -366,6 +367,18 @@ A sandbox should be short-lived and should be used to make small, iterative chan
.. sandboxes-best-practice-short-lived-end


.. _sandboxes-best-practice-small-test-audiences:

Very small test audiences
--------------------------------------------------

.. sandboxes-best-practice-small-test-audiences-start

To validate configuration updates for destinations use a manual workflow and a query to send a very small test audience from Amperity to the configured destination. Use the **LIMIT** clause at the end of the query to enforce the size of the very small audience. For example: ``LIMIT 10`` or ``LIMIT 100``.

.. sandboxes-best-practice-small-test-audiences-end


.. _sandboxes-howtos:

How-tos
Expand Down
5 changes: 3 additions & 2 deletions shared/destination_settings.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -486,10 +486,11 @@ Use the **Column name** setting to specify the name of the row number column in

.. setting-common-sandbox-recommendation-start

Use a sandbox to configure a destination for |destination-name|. Before promoting your changes, send a test audience, and then verify the results in |destination-name|. After verifying the end-to-end workflow, push the destination from the sandbox to production.
Amperity recommends using a sandbox to configure a destination for |destination-name|. Before promoting your changes to production from the sandbox, consider sending a very small test audience using a query and an orchestration to verify the results in |destination-name|. After verifying the end-to-end workflow, push the configuration changes from the sandbox to production.

.. setting-common-sandbox-recommendation-end
.. tip:: Learn more about `how sandboxes work <../reference/sandboxes.html>`__ and sandbox best practices such as `deleting sandboxes after configuration changes are promoted to production <../reference/sandboxes.html#sandboxes-best-practice-delete-on-promote>`__, `using short-lived sandboxes <../reference/sandboxes.html#short-lived-sandboxes>`__, and `sending very small test audiences <../reference/sandboxes.html#short-lived-small-test-audiences>`__.

.. setting-common-sandbox-recommendation-end

**Split outputs**

Expand Down