New Capture Selector Rule

We've added a new rule to Captures that allows you to trigger a Capture on a page when an element(s) defined by a CSS Selector:

  • Is present
  • Is not present
  • Contains a specified value
  • Does not contain a specified value
New Feature: CSS Selector Behavioural Rule for Gleam Capture

This provides you with an easy way to trigger Captures on pages which contain certain elements.

Learn more about Selectors in our in-depth guide.

In July, Twitter / X announced new Developer requirements for their API.

This included a change to the default rate limits for POST endpoints, which is one that we use heavily for one click Tweets, Follows and Retweets in campaigns.

At this stage Twitter / X has not approved our application to maintain previous POST rate limits for the following reason:

Do not (and do not allow your users to) simultaneously post identical or substantially similar content to multiple accounts.

This means that any Twitter / X actions that were once click to enter will now require multiple steps to first complete the action, then verify it (if you already Follow a specific account it'll continue to be one click).

We apologise for any impact this might have and we're continuing to explore options with Twitter / X to restore some (if not all) of this functionality.

See Next Article

Coupon Actions

Today we released a feature that allows you to use Coupons inside both Competition and Rewards campaigns as an individual action.