If enabled, split partner feed data by event name. If “Split Partner Feed Data by Event Name” checkbox is enabled, this setting is not used. Only applicable to feeds inputs, no effect on apps inputs. If not set, the partner name will be used. You must connect every input you want to store data for. Once your Data Warehose integration is configured, connect individual inputs to the Amazon Redshift output from the Connections page. If Data Hygiene is enabled, this is the age in days past which data is purged. If enabled, every 24 hours, mParticle will purge data over a certain age and perform vacuum and analyze commands on your database. Data deletion and a replay will be needed in order for existing tables to include this column. Note that this change does not apply retroactively to tables that have already been created. Store device application stamp in the mParticleDeviceID column. If enabled, individual columns are created for each user attribute Note that the minimum time is 1 minute and the maximum time is 24 hours (60 minutes x 24). The number of times a custom or commerce event name must be received in 30 day period for mParticle to create a dedicated table for that event.ĭelay Between Loading Sessions in MinutesĪllows you to adjust how often you want to load data into the data warehouse. Name of an existing schema where you want to store mParticle data. These credentials will be used when running queries from the mParticle UI. User ID for the readonlyuser user you created in your Redshift setup. These credentials will be used to manage the schema and load data. User ID for the dataloader user you created in your Redshift setup. The name of the database where you want to store mParticle Data. You can find this on the details page for your cluster in Redshift. With Amazon Redshift, the forwarding status reported by mParticle also represents the fulfillment status of the request, since mParticle knows immediately if the erasure request was processed successfully or not.Įndpoint string shown on Configuration tab on your Redshift Dashboard. The forwarding behavior for data subject erasure requests to Amazon Redshift is different than the behavior of other event integrations. Once the status has been set to Active, erasure requests are sent to Amazon Redshift immediately upon being received by mParticle. To forward data subject erasure requests to Amazon Redshift, set the Forwarding Status toggle to Active and select I understand after reading the disclaimer. Once your database is ready, you need to create groups with permissions to read and write data to the database.Ĭreate user dataloader in group readwritegroup password 'Aabcde123!' create user readonlyuser in group readonlygroup password 'Abcde123!' mParticle SetupĪfter adding Amazon Redshift from the integrations Directory, you can find the settings UI at Setup > Data Warehouse.įrom the main page for your Redshift configuration, select the Settings tab to provide the necessary settings to get your Redshift integration working. Create groups and users to manage permissions Within your database, create a schema to store your data. Choosing a different region increases latency between mParticle and Redshift. For example, if your mParticle pod is US1 or US2, create your Redshift database in us_east-1. The database should be in the same region as your mParticle pod. Create a Database and SchemaĬreate your Redshift Database. Enable the Integration Redshift Database Setup 1. You can work with your mParticle Customer Service Manager to load historical data. If enabled, performs data hygeine on your cluster every 24 hours to purge expired data and run vacuum and analyze commands.īy default, the integration begins loading current data into Redshift from the time it is enabled.Updates these views as new tables are created. Creates a view unioning all tables within each schema, and a view in the PUBLIC schema that unions the views of all schema.Adds new columns to tables when new events or user attributes are received.Less common events are recorded in a single table, labeled otherevents. Creates a table for each custom event name and each eCommerce event name with a volume above a defined threshold.The integration performs the following tasks in your Redshift cluster: MParticle’s Data Warehouse integration with Amazon Redshift forwards all your incoming data to a Redshift cluster, allowing you to query the raw data directly. Please ensure that your whitelist is up-to-date. Please note that as of we expanded the range of IP addresses used to forward customer data for Redshift.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |