Ingestly Endpoint v1.2.0

Breaking Changes

• The VCL now refers setting variables from dictionaries which configured through Fastly's Web UI. This means, the VCL itself does not contain setting variables. So, please set up dictionaries on the UI first, then replace the VCL with new one.
• Some response rules for older client (<1.0.0) has been removed. You need to update the client SDK before updating the Endpoint.

Changes

• Restructured the VCL.

Ingestly Endpoint v1.1.0

Breaking Changes

• Columns starting with device_ are restructured.
  • Removed device_os and device_platform
  • device_type is now set by Fastly side instead of Client side. (Device Atlas based)

Changes

• Added columns for device info.
• Added columns for bot detection.
• Added geo_postal_code

New feature

• In this version, requests for Safari's Private Click Measurement and Chrome's Attribution Reporting can be handled.
  • The well-known URLs such as ./well-known/attribution-reporting/* and ./well-known/private-click-measurement/* returns http 200
  • /ingestly-pixel/* returns http 302 to redirect requests to the "well-known" URL.

Ingestly Endpoint v1.0.0

This is a cumulative update for better data handling, ID management, new columns and the Consent Management.

Changes

• Session Management is now on Endpoint side instead of SDK side.
• Added some columns for storing SDK and Endpoint information.
• Added columns for Consent Management.
• Cookies for device identification and session management are now set without domain attribute, so the cookie is isolated within a domain name of the endpoint.
• The latest JS SDK does not save any IDs in Cookies or localStorage, and only the endpoint manages it.
• Improved HTTP headers.
• Added a path dedicated for the bulk ingestion which will be available in the next few months.
• A table schema for BigQuery has been fixed / updated to be compatible with nullable values.

How to update

1. Create a new table with the new table schema. (BigQuery only)
2. Update the Log Format and the destination table name for each databases on Fastly.
3. Update the Custom VCL on Fastly.
4. Activate the new configuration on Fastly.
5. Migrate records from the older table to the new table by INSERT SELECT. (BigQuery only)

Note

• This version is compatible with both SDK version 0.6.x and 1.0.0.

Ingestly Endpoint v0.2.1

• Added session_id and is_session_new columns

Ingestly Endpoint v0.2.0

• Added supports for Elasticsearch integration
• Added columns for Form Analysis
• Added columns for Ingestly Survey
• Added columns for Ingestly O2O
• Minor improvements