How Do You Send Each Customer a Personalized Package of Tableau Reports?

Imagine the account manager preparing a distributor’s monthly review. Sales is one report, Returns is another, and each must cover the same customer and period. A useful email contains the complete pack, rather than whichever attachment was ready first.

That assembly repeats for every distributor. ATRS Data-Driven Package Schedules can use maintained records to supply the reporting values and delivery instructions, then prepare the related Tableau Cloud reports together.

The customer should be recognizable throughout the work: in the report selections, filenames, message and destination. Keeping those instructions together helps the account team maintain the service as the customer list changes.

Conceptual illustration: Related reports brought together into a complete review pack.

For one customer with a fixed set of reports, an ordinary package may be enough. It can maintain the reports and delivery the account manager would otherwise assemble by hand.

A data-driven package is useful when the same reporting service repeats across customers or locations. Its driver supplies the values needed for each version, and grouping can bring reports for the same email address together.

Decide how the customer reads the pack. Separate Sales and Returns attachments may suit a detailed review; merged PDFs can provide one reading copy, while merged Excel outputs give finance one workbook. Choose that arrangement with the recipient before configuring the wider run.

Start with one distributor and a month the account manager knows. Assemble its Sales and Returns reports in an ATRS Data-Driven Package and use controlled test destinations for the first records.

Connect the driver to the maintained reporting query and inspect the selected rows. Choose the Key Column and map the customer, period and delivery values. Add the reports and preview their intended selections before combining them.

Set the attachment or merge arrangement the distributor accepted. Use meaningful report or worksheet names and a short message explaining the review period. Add the archive destination when the account team needs its own retained copy.

Open the complete delivery with the account manager. Then add a second customer and verify both packs side by side. A missing report and a wrong customer selection are different problems; try the failed-member response as part of the handover before enabling the full list.

The Data-Driven Package wizard keeps the package configuration together. Build its driver from the customer assignments your team maintains.

The account application may need another review pack between monthly runs. It can request the stored package after authorizing the intended audience and reporting scope.

The reporting owner maintains the customer selections, merge and destinations while the application follows the package execution.

POST /api/Schedule/ExecuteScheduleAsync
Authorization: Bearer <ATRS-access-token>
Content-Type: application/json

{
  "ScheduleType": "package",
  "UniqueId": 201,
  "RunBy": "Customer review package"
}

GET /api/Schedule/GetExecutionStatus?ExecutionId=<returned-id>
Authorization: Bearer <ATRS-access-token>

The account manager can open the monthly conversation with the customer’s complete review pack in front of them. The recurring assembly is maintained, leaving time to discuss why returns changed.

Bring one accepted customer pack and the records that identify its audience. They give you a practical starting point for personalized packages in ATRS.

Explore ATRS personalized report packages