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.

Buy this bolt-on

Typical use cases

• Pull nightly or 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
• Many reports can also be viewed in Reach Central

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
• What is excluded:

  • Real-time or streaming delivery
  • Password-based authentication
  • Custom report development

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 [e-mail].

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 [e-mail].
• 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: [e-mail]

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

Frequently asked questions

Can we use password authentication?

No. SFTP access requires an SSH key and IP allowlisting.

What happens after we purchase?

Reach collects your connection and encryption details.

Buy this bolt-on

Questions or clarification? Reach out to your respective account manager or email us at [e-mail] for help and support.