Store a copy of mPulse beacons in S3
Use Amazon's single storage service (S3) to upload and store your mPulse beacons.
Make sure that you have mPulse Administrator privileges and an Amazon S3 account. For more information on Amazon S3, see Get started with Amazon S3 and Amazon S3 FAQs.
Before you begin
mPulse provides beacon data via Amazon S3 logs. The logged data is derived from the raw data HTTP access logs, which is passed through several filters and transformers to arrive at a somewhat processed state that, if configured, is then stored in S3.
Note: The actual JSON-format beacon elements found in a given bucket will vary. The contents of your S3 store depend on the makeup of the domain for a given beacon, the site content, and the browser in use, as well as whether custom timers and custom metrics are configured for your account.
- Create an Amazon S3 bucket. For more information, see Working with Amazon S3 Buckets.
- In mPulse, click Central.
- In the left pane, click Apps, then double-click the app that you want to apply this option to.
- Select the Upload raw beacons to S3 checkbox.
- In the S3 Bucket Name field, enter the name of the S3 bucket that you created.
- In the S3 Region menu, select the Amazon server location. This is where you created the S3 bucket name. For example, US Standard.
- In the AWS Access Key field, enter your S3 account key.
- In the AWS Secret Key field. enter your S3 secret key, then click OK to save the configuration.
Give mPulse a few minutes to synchronize your information, then Access your S3 bucket. Download your file and open the raw beacon log in your preferred editor. You can use the JSON Formatter & Validator to understand the beacon structure as shown in this example.