What happened after reading (readers against non-readers)
GET /v1/changelog/entries/{entry_id}/after-reading
Builder and up. Over the 14 days after the entry published: readers are signed-in people it was shown to (the only readers with a user id to follow); non_readers are people known by user id before it published (from identify() or an earlier widget read) who were not shown it. A person is matched to Stripe by their user id in the customer’s metadata or by an email identify() linked to it. paid: their first ever paid invoice falls in the window. upgraded: they paid an invoice in the window larger than the one before it. signed_up is always null: a reader is known only by a user id the site gives people who already have an account, and anonymous readers are not linked to a person (not_computed says so). With no Stripe connection, paid and upgraded are null too. small_numbers is true when either group has fewer than 30 people or fewer than 5 events: read nothing into those rates. The numbers show what went together, not what the entry caused.
Auth: Secret key only. The dashboard has the same operation under /v1/dashboard/changelog.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”Responses
Section titled “ Responses ”Readers against non-readers
object
object
False while the window is still running.
object
object
object
object
object
object
object
object
object
Error envelope. See error.code for the discriminator.
object
object
object
Error envelope. See error.code for the discriminator.
object
object
object
Error envelope. See error.code for the discriminator.
object
object
object
Error envelope. See error.code for the discriminator.