Connect MixShift to Rig

    Sync Amazon Ads and retail history held in MixShift into Rig. MixShift keeps data well past the 60 and 95 day lookback of Amazon's own APIs, so this is how you get a multi-year Amazon Ads history. It connects with a client ID and secret that a MixShift admin creates.

    Before you start

    • You need to be a MixShift tenant admin, or ask one to create the credential for you.
    • The credential keeps every scope it is given. Do not restrict its scopes, because the daily history needs the SQL query scope as well as the Ads and retail read scopes.

    Step 1: Create a MixShift client credential

    1. Sign in to mcp.mixshift.io/admin as a tenant admin.
    2. Choose Create with raw secret. Do not use the plugin setup code, because it never gives you a secret that Rig can store.
    3. Enter a label. The label cannot contain spaces.
    4. Copy the client ID and the client secret straight away. MixShift shows the secret once.

    Read only by default
    MixShift credentials are read only unless an admin adds a write scope, and Rig only reads. You can revoke the credential at any time.

    Step 2: Connect it in Rig

    Adding a source needs a workspace owner, or a role with the Manage connections permission, on a workspace where you manage your own connections. If the Connectors tab says “Data ingestion for this workspace is managed by Rig”, ask an owner or Rig support to add the source.

    1. In Rig, open Connections, choose the Connectors tab and go to Sources & actions.
    2. Search for MixShift, open the card and click Connect.
    3. Client ID: The client ID from MixShift.
    4. Client secret: The secret MixShift showed you once.
    5. Account IDs: Optional. Comma-separated MixShift account IDs. Leave blank to sync every account the credential can see.
    6. Lookback days: Optional, from 1 to 366. Leave blank for 30 days on the Ads rollups and 366 on retail.
    7. Click Continue. Rig checks the credentials and lists the streams it can reach, so choose the ones you want and click Connect.
    8. The source then syncs on its schedule, which is nightly unless you change it. To load data straight away, click Sync on its row; Test pulls a small sample first if you want to check the connection.

    What Rig pulls in

    MixShift lands in its own mixshift schema in your warehouse:

    • Accounts: the MixShift accounts the credential can see.
    • Ads rollups: account summary, campaign performance, search terms and ASIN performance.
    • Retail: retail sales and retail traffic, with a row per day.
    • Brand Analytics: search query performance.
    • Daily Ads history: campaign, ad group, keyword and product ad tables by day, loaded one month at a time.

    The daily history streams are the route to history older than Amazon's own lookback.

    Good to know

    • MixShift tokens last 12 hours and Rig requests a fresh one for each sync.
    • The rollup streams cover a trailing window set by Lookback days. They do not backfill, so the daily history streams carry the long record.
    • MixShift limits each query to 50,000 rows, 10 MB and 120 seconds. Rig splits any month that goes over, down to a single day.
    • To disconnect MixShift, click the bin icon on the source's row under Sources & actions. Only whoever connected the source or a workspace owner can do this, and data already synced stays in the warehouse.

    What people use this for

    • Analyse Amazon Ads performance beyond Amazon's lookback
    • Find the search terms and keywords that earn their spend
    • Compare ads and retail performance by product
    • Track brand search demand

    More ideas for using MixShift

    MixShift documentation

    Was this guide helpful?