Skip to main content
Adobe deprecated SAINT classification FTP deliveries — move your Invoca classification data delivery to Adobe’s Classification Sets system to restore or avoid a gap in your classification data.

​
Overview

Adobe Analytics deprecated SAINT classification FTP deliveries on August 31, 2026. If your Invoca classification data delivery still uses FTP, move it to Adobe’s Classification Sets system now, which imports from cloud storage (Amazon S3) instead. The new system processes classifications in about 24 hours instead of about 72 hours, lets one classification set serve multiple report suites, and makes your classification data available in Adobe Experience Platform. Legacy classification rules (a related but separate Adobe feature) have a later deprecation date of February 28, 2027 — migrating your imports doesn’t automatically cover that.

​
Prerequisites

  • You must already be on Classification Sets in Adobe Analytics, not the legacy Classification Importer. This integration only works with Classification Sets.
  • You need the right Adobe permissions — either product admin access, or a product profile that includes Report Suite Tools > Classifications.
  • Your Adobe system administrator must allow account and location creation. If the setup options below are missing, ask your Adobe system administrator to enable them.
  • Decide who owns the configuration before creating it. A cloud account or location can only be edited later by whoever created it, or by a system administrator, and once shared with your organization it can’t be un-shared. Set this up under a long-tenured administrator’s account, not a contractor’s.
  • No firewall changes are required on your end — the storage bucket sits with Invoca, not on your network.

​
What you need to do

  1. Confirm or create a Classification Set in Adobe Analytics.
  2. Decide how to host the cloud storage: your own Amazon S3 bucket, or one Invoca hosts for you.
  3. If hosting your own bucket, gather your AWS Access Key ID, Secret Access Key, and bucket name (optionally, a delivery path, filename, and region), and share them securely with your Invoca contact. Bucket names can’t contain slashes, and delivery paths can’t have leading or trailing slashes.
  4. Submit a support case to Invoca to go live. Invoca then updates your integration, validates the first delivery, and disables the legacy FTP delivery — typically within 3-5 business days.

​
Using an Invoca-hosted bucket

If you’d rather not manage your own S3 bucket, Invoca hosts and manages one for you and delivers your classification data there — Adobe reads from that bucket automatically. You don’t need an AWS account or any file transfer process; Invoca gives you a Role ARN, and you configure Adobe to use it.
  1. Create a location account. In Adobe Analytics, go to Components > Locations > Location accounts and select Add account. Choose account type Amazon S3 Role ARN (not the legacy S3 type, which doesn’t support Classification Sets), and enter the Role ARN Invoca provided.
  2. Create a location. On the Locations tab, select Add location, set Use with to Classification sets, choose the account from step 1, and enter the bucket name and prefix (folder) Invoca gave you, including the trailing slash. A location can only serve one purpose, so don’t reuse a Data Feeds location for classifications.
  3. Create the classification set. This step is always manual — neither the cloud import process nor Adobe’s Classifications API can create one. Go to Components > Classification sets, create a new set, add a subscription for each report suite and key dimension you want classified (one set can cover multiple report suites), then add a classification for each column Invoca will deliver. Column names must exactly match your classification names, or imports fail with an “Unknown header” error.
  4. Configure automated ingestion. On the set’s Schema tab, select Automate, choose the location account and location from steps 1-2, set the list delimiter to comma and encoding to UTF-8, and add an email address (ideally a shared team address plus your Invoca contact) to notify when ingest jobs complete. Select Validate to confirm Adobe can reach Invoca’s bucket, then Save.
  5. Validate your first import. Once Invoca delivers the first file, check Classification sets > Jobs within 15 minutes, and compare the imported data against Invoca’s source file.

​
Good to know

Classification data always overwrites on conflict, so a bad source file will replace good data. Invoca keeps bucket versioning so a bad delivery can be identified and replayed — contact Invoca if you suspect this happened. Adobe doesn’t delete files after import; Invoca manages file rotation on the bucket, so you don’t need to. If validation fails in the Automate dialog, double-check the Role ARN, bucket name, and prefix, and send Invoca the exact error text. For any issue you can’t resolve on your own, contact Invoca Support.
Last modified on September 30, 2026