Sending Engagement Signals

Goal: Promoted wants to rank using engagement signals (impressions and actions)

Goal

Promoted uses EngagementEngagement - Impressions and Actions. signals to optimize your rankings.

Two main integration options

1. Proxy through your domain.

Forward engagement signals to your a proxy endpoint in your domain. For web, Promoted encourages these signals to either go through your server as a proxy or using a special DNS record so web browsers can avoid using 3rd party cookies and HTTP requests.

2. Call Promoted's APIs directly from Mobile.

Impressions

Promoted's ImpressionImpression - When an item is viewed on a screen long enough to count as an impression. E.g. >50% visible for >1s. data model is pretty simple:

  • A user identifier like logUserId.
  • Either InsertionInsertion - A response list contains a list of item Insertions. We start with more potential Request Insertions, then narrow down to a subset of Response Insertions to return to the UI. Insertions differ from Impressions because Insertions may not get viewed. ID or ContentContent - An item. Example: In a marketplace for buying and selling shoes, shoes are the content. ID so Promoted can join the Impression with backing InsertionInsertion - A response list contains a list of item Insertions. We start with more potential Request Insertions, then narrow down to a subset of Response Insertions to return to the UI. Insertions differ from Impressions because Insertions may not get viewed..
  • Timing information.

Promoted provides SDKs for tracking impressions on web, iOS and Android.

Actions

(UserUser - User-level data) ActionAction - Action taken by a user. For example, when an item is clicked on. include user-initiated behaviors like navigating, liking, sharing, checking out and purchasing.

Our Action data model is also pretty simple:

  • A user identifier like logUserId.
  • Either InsertionInsertion - A response list contains a list of item Insertions. We start with more potential Request Insertions, then narrow down to a subset of Response Insertions to return to the UI. Insertions differ from Impressions because Insertions may not get viewed. ID or ContentContent - An item. Example: In a marketplace for buying and selling shoes, shoes are the content. ID so Promoted can join the Impression with backing InsertionInsertion - A response list contains a list of item Insertions. We start with more potential Request Insertions, then narrow down to a subset of Response Insertions to return to the UI. Insertions differ from Impressions because Insertions may not get viewed..
  • Custom properties depending on the type of Action. E.g. shopping cart information. It's useful to attach properties that might help with debugging or stating your goal. If you want to pass a FeatureFeature - Variable in a machine learning model, including attributes of User, Content, etc. for our machine learning models, prefer to pass them on the RequestRequest - A request for a list of content, such as search, feed, or related items. and InsertionInsertion - A response list contains a list of item Insertions. We start with more potential Request Insertions, then narrow down to a subset of Response Insertions to return to the UI. Insertions differ from Impressions because Insertions may not get viewed. .

For more important actions (like purchase complete), it might make sense to log these directly from your server to minimize the risk of bad actors manipulating the log records.

If you have an Action that is not in our ActionType list, let Promoted know.

SDKs

Promoted provides Client Metrics Libraries and a Web Integration Guide to help. This includes impression tracking libraries.

Promoted's Data Infrastructure

Promoted does the work of joining the log records together and making them useful. You code does not need to join together Insertions, Impressions and Actions.


Did this page help you?