Revenue State Guard and Kit

This page is about the Kit side specifically: what RSG puts in your Kit account, what it changes there, what it will never touch, and how to take it out again. For what RSG does with your Stripe data, and what it costs, see How Revenue State Guard works.

What RSG puts in your Kit account

• —Tags it creates itself, named so you can see they are RSG's. It records the ID Kit returned when it created each one, and treats only those IDs as its own.
• —One entry in the “Exclude subscribers” setting of the sequence you designate — the tag that holds people out of it.
• —One webhook, so RSG hears about changes in Kit as they happen. It also re-reads the protected sequence, and the tags and email of a subscriber it has matched, on a schedule — Kit has no event for everything RSG needs to know.

What RSG changes in Kit, and what it never changes

RSG adds and removes its own tags on individual subscribers. It writes the exclusion entry when you set the sequence up, and at most once more in that sequence's lifetime: if its own entry later goes missing while everything you put there is untouched, it puts that one entry back, once. If it goes missing a second time, RSG stops instead of writing again. That is the whole of it.

• —It does not send email. Your sequences, your copy and your schedule stay yours; RSG only decides who is in them.
• —It does not create Kit subscribers, and it does not change anyone's subscription status or consent.
• —It does not write to your purchase history. If you use Kit's native commerce integration, that remains the source of truth for purchases.
• —It does not touch tags it did not create, and it does not rename or delete them.
• —It does not repair sequences it does not know about. Only the one you designate is protected.
• —It cannot recall an email that has already been sent. It stops the next one.

What leaves Kit

Only what RSG needs to tell one person from another and to check its own work: the Kit subscriber ID of anyone it has matched to a Stripe customer and the email the two were matched on, the IDs and names of the tags it created, the ID of the protected sequence and that sequence's exclusion settings as IDs, and your Kit account ID and name. Not your subscriber list, your custom fields, your email content, your broadcasts or your purchase history. The full disclosure is on Storing data outside Kit.

Connecting

RSG connects through Kit's OAuth, from the Setup page or from the app's page in the Kit App Store. It never asks for an API key. You then map each thing you sell to its Stripe prices, allow email matching, set your rules, and choose the sequence to protect. RSG changes nothing in Kit until that last step is done.

Checking what RSG has done

• —Activity lists every change RSG made in Kit, why it made it, and what Kit said when RSG read it back. A change is only reported as done once Kit confirms it.
• —Needs attention lists what RSG has stopped doing, and why. Two people sharing an email address, an email that changed after a match was made, or an exclusion setting that is not what RSG recorded all land here rather than being guessed at.
• —RSG re-reads the protected sequence's settings on a schedule, so a change it did not make is caught before a wrong email goes out rather than after.

If you edit a protected sequence yourself

Kit does not let two things edit a sequence safely at the same moment. If you change a protected sequence's exclusion settings in the same second RSG writes to it, one of the two edits can be lost. RSG narrows that window as far as it can, writes that setting at most twice in a sequence's lifetime, never overwrites something it did not add, and tells you whenever what it sees is not what it wrote. It cannot make the window disappear, and it will not claim otherwise.

The one repeat write is narrow on purpose. RSG only restores its own entry when that entry is the single thing missing and everything you put there is intact. If it finds an entry you added, changed or removed, it does not write at all: it stops claiming protection for that sequence and says so on Needs attention, rather than overwriting a change you may have made deliberately.

Removing RSG

Disconnect from the Setup page, or uninstall the app in Kit. RSG removes the one exclusion entry it added and deletes its webhook while it still has access. Tags stay on your subscribers: stripping your segmentation on the way out would do more damage than leaving it. What happens to the data RSG holds is on Privacy.

Getting help

Email masanori.iwata@orumio.com. Include the reference shown on any error, and we will reply within one business day.