Custom SFTP Setup

Deliver standard Reach reports to your systems through a secure SFTP drop.

Overview

This bolt-on delivers standard Reach reports to an SFTP folder owned by your brand.

• What it is: A secure SFTP “drop” for scheduled report files.

• Why teams use it: Feed reports into BI, reconciliation, or downstream systems.

• Who it is for: Operations, finance, analytics, and your IT/security team.

SFTP access uses SSH keys plus IP allowlisting. Password logins are not supported.

Typical use cases

• Pull nightly/weekly report files into your data stack.

• Reconcile usage and billing with internal systems.

• Provide controlled access to a trusted external partner.

How access works

• Each brand gets an isolated folder.

• Parent brands can receive aggregated files when brand hierarchy is configured.

• Many reports can also be viewed in Reach Central, depending on roles.

Scope

• What is included:

  • Brand-specific SFTP user and folder setup.

  • Delivery of supported standard reports on an agreed cadence.

  • SSH key authentication and IP allowlisting.

  • Optional GPG encryption for files stored on SFTP.

• What is excluded:

  • Real-time or streaming delivery.

  • Password-based authentication.

  • Custom report development (scoped separately).

Brand inputs

Send the following to Reach:

• Egress IP address(es) to allowlist (public IP your SFTP client connects from).

• SSH public key (for key-based login).

• GPG public key (optional, if you want encrypted .gpg files).

• Whether you need parent-level aggregated reporting (if applicable).

Setup flow

1

Prepare access details

Collect allowlist IPs and your SSH public key.

If you want encryption, also prepare a GPG public key.

2

Email the setup package

Send everything to [email protected].

3

Reach provisions access

Reach creates the SFTP user and configures folder permissions.

4

Validate and confirm delivery

Reach shares the endpoint, username, and folder path.

You confirm you can connect and download files.

Troubleshooting

• Connection refused

  • Your connecting IP likely isn’t allowlisted.

  • If your IP changed, email the new IP to [email protected].

• Authentication failed

  • Your private key doesn’t match the registered public key.

  • Confirm you’re using the same keypair you shared during setup.

• Encrypted files won’t decrypt

  • Confirm the correct GPG private key and passphrase are available.

• Aggregated parent report is missing a child brand

  • Confirm parent/child brand mapping is current.

Setup, access, and delivery issues: [email protected]

Requesting this bolt-on

For the standard request process, commercial notes, and support, see Bolt-ons catalog.

Technical details

For the implementation-specific setup details, visit: Brand SFTP set-up technical details

Questions or clarification? Reach out to your respective account manager or email at [email protected]