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

The following new features were included in the latest release of SAS 360 Match:   The privacy shield feature is available to all customers. You can use the privacy shield feature to create rules that control the information that a third-party ad server can capture about your audience. The rule limits the information that you give to the external party from the original client request. For more information, see Managing Privacy Shields.   The named exposure policies feature is available to all customers. You can use an exposure policy to set exposure levels across multiple items to limit how often SAS 360 Match serves a specific response. For more information, see Managing Exposure Policies. ... View more

The latest release of SAS 360 Match includes the following updates and changes: The UI for Targeting>Connectors has been updated to improve the user experience. The functionality remains the same. You might notice minor UI modifications. The older version of connectors has been removed. SAS 360 Match supports the upload of a text creative that contains Javascript. You can no longer create custom format fields that contain hyphens. NOTE: Any existing custom format fields that use a hyphen that are saved cannot be used as tokens in creatives. ... View more

The latest release of SAS 360 Match contains the following updates.   REST API Updates   Additional commands were added to the REST APIs:   Retrieve a campaign by status (status_equals😞 The available values for the filter are active, inactive, closed, alerted, or active_or_inactive (not_closed) Filter using the null to retrieve all items with a null field Filter using equals_or_null, lte_or_null, or gte_or_null to retrieve the items where a field either is null or equal to, less than, or greater than a specified value. For more information, see the Campaigns and Filtering topics in the API Docs that are available in the application.   New Alerts Available   You can receive alerts for the following entity types:   Connector Event Network Placement PrivacyShield Snippet SupertagValue Tier To see your alerts, navigate to My Work > Alerts in the application. ... View more

The latest release for SAS 360 Match includes the following updates: A new option in the Usage report to retrieve daily and monthly billing metrics for ad requests, events, and peak capacity units An update to the creative preview so that it uses the specified format template instead of the default template ... View more

The latest release of SAS 360 Match includes the following changes: Added improvements to the user interface to configure the peak capacity feature that manages sporadic and significant traffic spikes Updated the Outage report to displays date and time information in the user’s time zone Fixed errors that are occasionally received when searching flights Enabled the BI workflow cube to display additional contact details ... View more