The following new features are now available in SAS 360 Match:   You can use IPADDRESS and GEO_IP tokens to refer to an IP address when you integrate with third-parties or in creative responses. Use FIRSTLOOK=<tier name> in an impression request to select an ad from the tier that is named in the FIRSTLOOK tag and conduct the selection without visitor context. The tag enables you to skip regular ad selection and replace it with an ad from the FIRSTLOOK tier. For more information, see FIRSTLOOK Tag in the Advanced Features Guide. Use the REQPRIORITY tag to identify the relative importance of specific requests to each other. The higher-priority requests are handled first when the network is busy. Using the REQPRIORITY tag prevents clients from timing out while waiting for replies during a traffic spike on the network. For more information, see Prioritizing Requests in the Advanced Features Guide.  As noted in the Advanced Features Guide, this feature will only be of benefit to SAS 360 Match Premium subscribers.   The following new features will be available in SAS 360 Match beginning Tuesday, September 2nd, 2025 at 9am EDT:   The Eliminate Duplicate Tags option prevents an advertiser from serving tag again if the tag has already been served to the same view ID. This option is useful when more than one dataset is active within a single view ID. You can specify the tag that SAS 360 Match should serve only once to the same view ID. You can include token references in tags and add them to a target rule. The token can appear anywhere within the target rule, e.g. "abc%%tag1%%def%%tag2%%xyz". For more information, see Token References in Targets. ... View more

The latest release of SAS® 360 Match includes an updated landing page. The new homepage enables a user to understand recent changes, provides options for common tasks, and links to useful information, alerts, and notifications.  ... View more

The latest release of SAS 360 Match includes the following new features:   Support for multiple datasets and the ability to organize the data sets in a specific order. For more information, see Evaluating Multiple Data Sets and ORDERBY Tag in the Advanced Features Guide. The DATEDELTA token that adds or subtracts a specified number of days to a date token that is in the YYYY-MM-DD format. For more information, see DATEDELTA. Dot notation and new tokens for advertisers, campaigns, creatives, flights, flight creatives, and tiers in creative templates. For more information, see Predefined Tokens.   With the addition of dot notation and new tokens for templates, the following tokens are deprecated and replaced with new tokens.   ALTIMAGE replaced with CREATIVE.ALTIMAGE ALTTEXT replaced with CREATIVE.ALTTEXT CLICKDESTINATIONURL replaced with CREATIVE.CLICKURL CRTUINFO replaced with CREATIVE.UINFO HEIGHT replaced with CREATIVE.HEIGHT MEDIA replaced with CREATIVE.MEDIA WIDTH replaced with CREATIVE.WIDTH ... View more

The latest version of SAS 360 Match contains the following changes and features: The ability to specify the number of format templates that can be associated with a format. The default is 10. Contact SAS Technical Support to change the default value. Ensures that team-restricted users cannot bypass restrictions on campaigns and tiers by using the API. Now the API prevents team-restricted users from assigning a flight to a campaign or a tier that is not assigned to their team. There is no change in the UI where the options provided to a user were already correctly restricted. ... View more

The latest version of SAS 360 Match includes the following new features: New predefined tokens FLIGHT.END_DATE, TIER.NAME, and TIER.ID.  For more information, see Predefined Tokens. The ability to request SAS Technical Support disables the user agent checks or bot checks while keeping fraud detection enabled. This setting is useful when Match requests are embedded in email or when Match is used with other non-browser clients. The latest version of SAS 360 Match includes the ability to generate a OAUTH Bearer (JWT) token that the user can then use to authenticate a request. Use the API to request a token. To manage the token, navigate to Administration > OAUTH Applications in the user interface.   For more information about the OAUTH implementation in Match, see the OAUTH Authorization Guide.   Note: This feature is being rolled out as Limited Release and might not be available for your tenant yet. Contact your SAS representative if you have questions about this feature's availability. ... View more

An updated landing page for SAS 360 Match now available for some customers. The new homepage provides an updated user interface and enables a user to quickly understand recent changes, provides options for common tasks, and links to useful information, alerts, and notifications.   This feature is in release preview and is available on some development tenants. For more information, contact your SAS representative. ... View more

The latest release of SAS 360 Match includes the following updates: Reports for flight priority use new optimized tables. Customers can delete unprocessed files that were uploaded using the UserReg API. Users with view permission can view flight creatives. Previously, users were required to have edit capabilities before they could view flight creatives. The %%BOTFRAUD%% token that indicates whether fraud is detected and the type of fraud. For more information, see Predefined Tokens. ... View more

In the latest version of SAS 360 Match, the user interface for Targeting > Sizes has been updated to improve the user experience. The new user interface includes a separate History tab that enables you to view more information about the activity history for the size definition.   This feature is limited release and is available on your development tenants. ... View more

In the latest update of SAS 360 Match, you can specify a primary size and additional sizes in a placement. When you specify multiple sizes, the bid request creates a bid from the intersection of the sizes in the ad request and the Size and Other sizes fields in a placement. For example, an ad request that specifies sizes A, B, and C and a placement with Size set to B and Other sizes set to C, D, and E will only use sizes B and C in bid requests and only those sizes are mapped for the network.   Contact SAS Technical Support to enable the option to reduce bid sizes to those that are in both the ad request and placement. By default, SAS 360 Match uses all request sizes with network size mappings only. ... View more

The following improvements and new features were added to SAS 360 Match recently:   An update to locale handling to support and use the locale that is provided by a user’s web browser unless the user’s profile in SAS 360 Match has specified a locale. If you notice a change in how dates are formatted, your browser could be sending a locale that is different than the default locale that was used previously. Reset the user’s local in the user profile to revert to the prior behavior. The redirect allowlist no longer allows a duplicate URL. A request to download a file that does not exist results in an HTTP 404 status code instead of 200. The expression of a MIME type on a creative format is only effective for network creative formats.  The UI and API have been updated to remove the field for other creative formats. ... View more

The latest release of SAS® 360 Match includes the ability to specify a creative format for a placement in the user interface. The creative format enables a user to render a user-specified bid response that overrides the default bid response creative.   In addition, the feature includes a new format template that provides users with access to individual fields in the bid response JSON in a format token. For more information, see Structured Tokens - BIDRESPONSE. ... View more

The latest release of SAS® 360 Match includes:   The user interface for connectors and privacy shields have been updated to improve the user experience. The Eliminate Duplicate Categories option for a tier.  When the option is selected, it prevents a flight or creative from serving if the flight or creative contains any categories that have already been served to the same view ID, regardless of advertiser.   The new user interface includes a separate History tab that enables you to view more information about the activity history for connectors and privacy shields. The additional details include information about changes to the item, including a link to the details of the change that lists the field that was changed, the original value, and the new value, as well as a window with overflow information.     ... View more

The latest release of SAS 360 Match includes the following improvement: The process that is used to validate a target has been streamlined to improve its performance, especially in cases when a registered tag included in the target could contains a very large number of possible values. ... View more

The most recent update of SAS 360 Match includes the following updates: A user with edit permission for ApiKey can reset their own API key without requesting help from SAS Technical Support. To reset the API key, navigate to Admin>User and enable the Regenerate API Key check box. API documentation is now available for /currencies/base.xml. For more information, navigate to API Docs from the user interface and select Currencies. ... View more

The latest release of SAS 360 Match enables administrative users to create an allowlist that specifies the URLs that an ad server can safely redirect in an ad request. This check is normally applied to the creative formats that use a PRECLICKURL token. For more information, see About Redirect Allowlist. ... View more