Connect Alia to Rig

    Sync your Alia popup and quiz data into Rig: campaigns and their popups, daily signups, opt-ins and views, attributed orders and sales, quiz answers and visitor context. Alia connects with an API key that you create with three read scopes.

    Before you start

    • You need access to the Alia dashboard to create an API key.
    • Alia's API returns only totals and no individual events. Rig stores the totals as one snapshot per completed day, so the history builds up day by day.

    Step 1: Create an Alia API key

    1. Open your Alia dashboard and find where API keys are created. Alia's API documentation says keys are made in the dashboard but does not name the menu.
    2. Create a key and tick the scopes read:merchant, read:events and read:segments.
    3. Copy the key and keep it safe.

    Each scope unlocks its own streams
    A missing scope hides only the streams that need it, and Rig lists them as unavailable when you connect. read:merchant covers the account, read:events the stats and distributions, and read:segments the campaigns.

    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 Alia, open the card and click Connect.
    3. API key: the key from Step 1.
    4. Days of history on first sync: pre-filled with 90. Leave it as it is unless you want a different window. A long window is spread over several nightly runs.
    5. Context distribution properties: pre-filled with country,device,browser,utmSource,utmMedium,utmCampaign. Leave it as it is, or trim it to the properties you use, because each one costs a request every day.
    6. Click Continue. Rig checks the credentials and lists the streams it can reach, so choose the ones you want and click Connect.
    7. 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

    Alia lands in its own alia schema in your warehouse:

    • Merchant: your account identity, including the Shopify store it belongs to.
    • Campaigns: campaigns with their popups, including archived ones.
    • Daily stats: an account-wide row per day covering signups, opt-ins, views, bounce and attributed orders and sales.
    • Campaign daily stats: a trimmed funnel for each campaign and day.
    • Poll answer distributions: quiz answers grouped by question, per day.
    • Context distributions: visitor context per day, such as country, device and UTM values.

    Alia limits requests with a token bucket that grows with your Alia plan, and stats requests cost more than most. A long first backfill therefore runs over several nights.

    Good to know

    • Attributed orders and sales use a 30-day attribution window after signup.
    • Alia exposes 15 visitor context properties, including path, domain, region, city and Shopify market. Only the six in the default list are read unless you add more.
    • Per-campaign stats use a smaller set of eight measures than the account-wide stats, so rates are worked out from the counts.
    • To disconnect Alia, 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

    • Compare capture campaigns on revenue, not signups
    • Use quiz answers as zero-party data
    • See which traffic converts to capture

    More ideas for using Alia

    Was this guide helpful?