Connect Storyclash to Rig

    Sync Storyclash influencer campaigns, creator posts and per-creator commerce attribution into Rig, so creator performance sits beside your orders. Storyclash gives each customer an external API token, and the API allows one request an hour per campaign.

    Before you start

    • You need an external API token from Storyclash. Storyclash issues it on request, so ask your Storyclash contact for it.
    • Leave an hour between syncs. Storyclash allows one request per hour per campaign.

    Step 1: Request your Storyclash API token

    1. Ask your Storyclash contact for a token for the external API. Storyclash's integration page explains how to request API access.
    2. Copy the token and keep it secret. Anyone with it can read your campaign data.

    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 Storyclash, open the card and click Connect.
    3. External API token: Paste the token Storyclash gave you.
    4. Click Continue. Rig checks the credentials and lists the streams it can reach, so choose the ones you want and click Connect.
    5. 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

    Storyclash lands in its own storyclash schema in your warehouse:

    • Campaigns: every campaign on your account.
    • Campaign posts: creator posts in each campaign, with their reach and performance metrics.
    • Campaign creators: the creators in each campaign, with discount code, conversions, revenue and ROAS where Storyclash tracks them.

    Good to know

    • When Storyclash throttles a request it answers with a normal-looking response that says the rate limit was reached. Rig treats that as a failed sync instead of writing empty tables, so run the next sync an hour later.
    • Rig requests each campaign page once per sync, which is why one sync every hour is the practical maximum.
    • The token sits in the request address, so Rig keeps it out of error messages and run history.
    • To disconnect Storyclash, 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

    • Rank creators on contribution, not followers
    • Check discount code attribution against orders
    • Track campaigns and content over time

    More ideas for using Storyclash

    Storyclash documentation

    Was this guide helpful?