A portal user within RevCent allows you to offer third parties a way to view specific sales data by logging into an Metric Portal.
Please read the important concepts below in order to successfully display aggregations to portal users.
RevCent must know who the portal user is in order to display sales aggregations for that specific portal user. You will need to specify the metadata for each portal user so RevCent knows which sale to attribute to a particular portal user. RevCent will know who the portal user is only if you have properly attached metadata to a sale. Continue below to #2.
RevCent uses the portal users' metadata, and matches the metadata with sales when conducting aggregations. If the metadata name and value pair(s) in a portal users account does not match the sale metadata name and value pairs in a sale(s), the portal user will not see any aggregations for that sale(s). View the metadata matching section for detailed information. Continue below to #3 for information on attaching portal user metadata to a sale via conversion tracking.
Important: view the Conversion Tracking page for information on setting up a tracking domain, amending landing page URLs and ultimately attaching a portal users' metadata name value pair to a sale.
Note: WooCommerce users only need to set up a tracking domain(s) and URL parameters, the metadata attachment to sales is done automatically via the RevCent plugin.
View all portal users by clicking the Metric Portals > Portal Users link on the sidebar.
Create a new portal user by clicking the Create New Portal User button when viewing all portal users, or click the Add Portal User button within the Metric Portal you wish to add the portal user to.
Set the portal users' first name.
Set the portal users' last name.
Set the portal users' email. This cannot be changed once the portal user has been created.
Set the status for the portal user.
Select one or more metric portals to add to the account. A portal user can have access to multiple portals.
Select an existing tab from your dashboard that you wish to display, specific to the portal user, when they view their dashboard. If none selected, default portal tab will be used. The portal user dashboard is a simplified version of the RevCent dashboard which only allows portal users to filter by date, and not modify any settings.
Important: The dashboard tab you select will be the exact layout, with panels containing the exact query aggregations, that the portal user will see when logged in. The only difference is the tab panels will display query aggregations for sales matching their portal user metadata. Portal users will not have the ability to change any settings, filters, or query aggregations. Any changes you make in your dashboard to the tab you select is reflected in the portal users' dashboard. You need to make sure you pick the right panels and aggregations when creating the dashboard tab meant for portal users. For example, you probably don't want to display a profit panel to portal users.
Add a custom rolling reserve percentage, specific to the portal user, that will be deducted from amounts displayed. If not enabled, default portal rolling reserve will be used.
Enter the portal user password. Write this down, this is not retrievable later. You can always reset the portal user password.
One of the most important parts of the metric portal system in RevCent. You must attach one or more name value pairs of metadata to the portal user. RevCent will use the portal users' metadata, and matches the metadata with sales when conducting aggregations.View the metadata matching section for detailed information.
Edit an existing portal user by clicking the edit icon when viewing all portal users.
Set the portal users' first name.
Set the portal users' last name.
Set the status for the portal user.
Select one or more metric portals to add to the portal user. A portal user can have access to multiple portals.
Select an existing tab from your dashboard that you wish to display, specific to this portal user, when they view their dashboard. If none selected, default portal tab will be used. The portal user dashboard is a simplified version of the RevCent dashboard which only allows portal users to filter by date, and not modify any settings.
Important: The dashboard tab you select will be the exact layout, with sales panels containing the exact query aggregations, that the portal user will see when logged in. The only difference is the tab panels will display query aggregations for sales matching their portal user metadata. Portal users will not have the ability to change any settings, filters, or query aggregations. Any changes you make in your dashboard to the tab you select is reflected in the portal users' dashboard. You need to make sure you pick the right sales panels and aggregations when creating the dashboard tab meant for portal users. For example, you probably don't want to display a profit panel to portal users.
Add a custom rolling reserve percentage, specific to this portal user, that will be deducted from amounts displayed. If not enabled, default portal rolling reserve will be used.
One of the most important parts of the metric portal system in RevCent. You must attach one or more name value pairs of metadata to the portal user. RevCent will use the portal users' metadata, and matches the metadata with sales when conducting aggregations. View the metadata matching section for detailed information.
RevCent uses the portal users' metadata, that you set when creating or modifying a portal user in RevCent, and matches the metadata with sales when conducting aggregations. If the metadata name and value pair(s) for a portal user does not match the sale metadata name and value pairs in a sale(s), the portal user will not see any aggregations for that sale(s).
Below are scenarios where metadata will match or not match based on the metadata of a portal user and the metadata of a sale.
Portal user metadata:
"metadata": [ { "name": "portal_user_id", "value": "12345" } ]
1. Will include the sale when aggregating metrics. Reason: Name and value both match.
Sale metadata:
"metadata": [ { "name": "portal_user_id", "value": "12345" } ]
2. Will include the sale when aggregating metrics. Reason: Name and value both match regardless of additional metadata entry.
Sale metadata:
"metadata": [ { "name": "portal_user_id", "value": "12345" }, { "name": "landing_page", "value": "blue" } ]
1. Will not include the sale when aggregating metrics. Reason: Same name but mismatched value.
Sale metadata:
"metadata": [ { "name": "portal_user_id", "value": "56789" } ]
2. Will not include the sale when aggregating metrics. Reason: Same value but mismatched name.
Sale metadata:
"metadata": [ { "name": "portal_user_id", "value": "12345" } ]
3. Will not include the sale when aggregating metrics. Reason: No metadata name match.
Sale metadata:
"metadata": [{ "name": "landing_page", "value": "blue" }]
4. Will not include the sale when aggregating metrics. Reason: No metadata in sale.
Sale metadata:
"metadata": []