How RocketJuice works with Meta

What we do with a brand's Meta account, in plain language.

1. 1

   Your brand connects its own Meta account

   You sign in with Facebook and choose which of your own ad account, Page, Instagram account and conversions dataset RocketJuice may work with. We read their names and IDs so you don't have to paste them by hand. You can disconnect at any time.

2. 2

   The creator approves the partnership in their own Instagram account

   Before a partnership ad can run, the creator you are working with approves the branded-content partnership themselves, from inside their own account on Instagram. We cannot do this for them, and we never try to.

3. 3

   You approve a video, and we place it in your own ad account

   Once you approve a creator's video, RocketJuice places it as a partnership ad in your own connected ad account. It is created paused by default: nothing runs, and nothing spends, until you turn it on yourself. Only you can choose to launch it as active instead, and we ask you to confirm that choice before we place the ad.

4. 4

   We read that ad's results, so what you owe reflects what the video actually sold

   We read that ad's results - what it spent, and the purchases it drove - from your own ad account, so the commission you owe the creator is based on what their video actually sold, not an estimate. We read nothing else from it.

5. 5

   If they take that permission back, we pause the ad automatically

   A creator can withdraw a branded-content partnership at any time, in their own Instagram account. RocketJuice checks every hour and pauses the partnership ad it placed with them within an hour of the withdrawal - no one has to remember to do it by hand.

6. 6

   What we never do

   We never post or message as you, never read your Page's content beyond what running the partnership requires, never use one brand's data for another, and never sell data. Your data - the asset ids, the ad results, the permission records and the videos you approve - is stored in the EU, in Google Cloud's Frankfurt region. The credentials that let us work with your Meta account are held in Google Secret Manager, never in our database and never in a browser.