Overview
Adobe Analytics is a first-class Lens source, sitting alongside GA4. The difference is how Adobe's reporting API works. Where GA4 happily returns several dimensions in one report, the Adobe Analytics API breaks down by a single dimension per request. Lens works within that limit by always pairing your chosen dimension with the date, then making one report request per day in the sync window and stitching the days together.
The practical result is a table shaped as date by your dimension. If you pick page as the dimension and pageviews as the metric, you get one row per page per day. That is exactly the breakdown report most Adobe clients live in, and it feeds Lens boards, KPI tiles, and shared reports like any other table.
Add an Adobe table
Open Lens > Tables from the left sidebar and click Add Table. Choose Adobe Analytics as the source type, then give the table a clear name. The name is for your own organization, so something like "Veritiv Pageviews by Page" makes the table easy to find later.
Enter the report suite
Fill in the Report Suite ID (rsid), for example veritivcorpglobalprod, and the Global Company ID, for example veriti0. Together these tell Adobe which suite to pull from and under which company account. Both values come from your Adobe Analytics admin console; if you are unsure, your Adobe administrator can confirm them.
You do not enter an Adobe client ID or secret on the table. Lens reads the same Adobe API credentials that Observer uses, stored at the property level. If Observer already connects to Adobe for this property, Lens is ready to go.
Set the report suite timezone
Enter the IANA timezone of the report suite in the Report Suite Timezone field, for example America/New_York. Adobe reports its daily numbers in the report suite's own timezone, so Lens buckets the daily rows the same way. This keeps the dates in Lens lined up with what you see in the Adobe UI. If you leave the field blank it defaults to America/New_York.
If your dates look shifted by a day compared to the Adobe interface, the timezone here does not match the suite's actual setting. Confirm the suite timezone in Adobe and update this field, then re-sync.
Choose one breakdown dimension
Under Breakdown Dimension and Metrics, enter a friendly column name and the Adobe ID. The friendly name (for example page) is what appears on boards and reports. The Adobe ID (for example variables/page) is the identifier Lens sends to the Adobe API. Splitting the two means a slash in the Adobe ID never interferes with your clean column name.
Lens adds the date dimension automatically, so you only choose the one breakdown. If you need to report on a second dimension, build a separate Adobe table for it. You can place both tables on the same board, or combine them by date where that makes sense.
Add metrics
Add one row per metric under the Metrics section. Each row takes a friendly name (for example pageviews) and the Adobe ID (for example metrics/pageviews). Click Add Metric for each additional metric you want in the table. As with the dimension, the friendly name is for display and the Adobe ID is what gets requested.
Set backfill and sync mode
Set Backfill Days to control how much history a full refresh pulls. The default is 90 days. Because Lens makes one Adobe API call per day in the window, a larger backfill takes proportionally longer, so a 90-day backfill is 90 calls. Choose a sync mode: Full Refresh re-pulls the entire backfill window, while Incremental pulls only the most recent days on each run. Pick a schedule (Hourly, Daily, Weekly, Monthly, or Manual), then click Save and Sync.
Troubleshooting
Sync fails with an authentication or permission error
Lens uses the property's Adobe credentials, the same ones Observer relies on. If the sync cannot authenticate, confirm the Adobe API connection is set up for this property and that the credentials have access to the report suite you entered. An Adobe admin may need to grant the API user access to that suite.
Dates are off by one day
This is almost always a timezone mismatch. Adobe buckets days in the report suite timezone, so set the Report Suite Timezone to match the suite's actual setting in Adobe, then re-sync.
A large backfill is slow
That is expected. Each day in the window is a separate Adobe API call, so a long backfill runs many requests in sequence. Use a smaller backfill window for the first sync, or run the initial full refresh off-hours, then keep the table current with incremental syncs.
I need more than one breakdown dimension
Adobe's API breaks down by a single dimension per report, so Lens does too. Build one table per dimension and combine them on a board. Note that joining by date alone will not reconstruct a true multi-dimension cross-tab, because the shared date key fans the rows out.