creator.follow.created replaces the legacy follow.new event, and the post events have no legacy equivalent.
Each event arrives in the envelope, and the tables below describe
data. For the same activity through the API, use Get followers and Get comments for a post.
Follow resource
creator.follow.created uses this resource. Follows have no external id, so the identity is the (follower, creator) pair.
tracking carries { link_url, metadata } for the follower. The block is null when the follower carries neither a tracking parameter nor an impression on one of this creator’s links. link_url is the follower’s platform-wide last-touch parameter and metadata is scoped to this creator, so the two can disagree. Tracking links explains how creators set them up.
creator.follow.created fires on every created follow. The legacy follow.new stays behind the follow-notification throttle, so the two events don’t fire one-for-one. Don’t treat a missing follow.new as a missing follow.Example: creator.follow.created
Post resource
creator.post.liked and creator.post.commented share this resource. A like has no external id (id is null), while a comment carries its own UUID in id and its text in comment_text.
The post events carry no
tracking block.
Example: creator.post.commented
creator.post.liked uses the same shape with id: null and comment_text: null.