FAQs
Frequently Asked Questions
Last updated
Was this helpful?
Frequently Asked Questions
Last updated
Was this helpful?
Welcome to our FAQ page. Here, you'll find answers to common questions and helpful information about Netmera. Explore the topics below to get the most out of your experience with Netmera and discover the full potential of our powerful engagement platform. If you have any further inquiries, feel free to reach out to our support team for prompt assistance.
This cannot be done. Instead, you can provide daily exports via to the customer. Alternatively, our panel supports a "fallback" mechanism for SMS sending to users who did not receive the push. While you're creating your notification on step "What" you may set up fallback mechanism.
No, the user limit cannot be set via the REST API.
No, adding the "Add Buttons" (interactive) feature cannot be done via the API. However, it is possible to add the interactive feature for push notifications created within the Netmera Panel. Please refer to Button Sets.
Yes, we have a system in place. In case of rare issues with push notifications, our operations team receives alerts and communicates with the customers to provide relevant information.
No, "Send All" does not reach users who were not integrated with Netmera before. Segments should be used to target those users. Please refer to Define Segment.
No, our web push notifications are sent through Google CDN, so recalling them is not possible.
Amazon SES is the platform where you manage your sending quotas. There are two main quotas are set by Amazon SES and the exact number of email quotas change for each account.
Total number of emails that can be sent within 24 hours: This is the overall limit for the number of emails that can be sent in a 24-hour period.
Number of emails that can be sent per second: This represents the maximum rate at which emails can be sent in one second.
Above you may see a sample sending limits image on Amazon SES Account dashboard. In order to monitor your own sending quotas using the Amazon SES console please see the following document.
The panel provides device-based data in funnels. If you export the data using tagging, it provides user-based data.
Yes, there is a limit for event attributes. The maximum number of attributes is 25, with varying limits for different data types.
When filtering for the same event over the same date range on different days, you might notice variations in the reported values. This is due to how our system manages offline events:
Offline Event Handling: When a user logs in while offline, the event is recorded with the correct timestamp and stored locally.
Synchronization: Once the device reconnects to the internet, or when the user logs in again, these offline events are sent to our database.
As a result, you may see an increase in event values over time as offline events are processed and added to the data. This means that values for the same date range may grow as more data becomes available. The benefits of this approach are:
Maintain Data Accuracy: By recording events with their original timestamps, we ensure accurate reflection of all user actions, even if they occur while offline.
Enhance Reliability: Storing events locally prevents data loss during temporary connectivity issues, providing a more complete view of user interactions.
This method allows us to deliver accurate and reliable data, accommodating users' varying connectivity conditions.
To improve page performance, we use a calculation module that processes data efficiently. As a result, some variations in data may occur as the number of events and users in a funnel increases. These variations can appear both positively and negatively.
For instance, adding a single event to a funnel might show a different user count compared to when additional events are included. The user count can decrease or increase slightly as more steps or data are added.
Despite these minor variations, the standard level of discrepancy is very low, and the funnel data remains highly reliable for analysis. If exact user data is required, you can export the data to obtain precise figures. The export provides accurate information not affected by the on-screen display discrepancies.
Note on Exported Data:
In cases where export data appears shows lower data than on-screen Funnel page, there are a few potential reasons:
Standard Discrepancy: The discrepancy might be more noticeable in export data due to the upward variation compared to the on-screen data. This means that the export may sometimes show less data than the on-screen display.
Excluded User Data: If users who previously triggered events are no longer registered in the system (e.g., they have been removed or their data has been deleted), their information will not appear in the export. Consequently, if tags or external IDs are used for export, the data will not include them because these users are no longer available.
Netmera's cookies start with "n". Additionally, Netmera now uses local storage instead of cookies. All the cookies used by Netmera are shared on the relevant page.
Our SDK retrieves the timezone information from the user's device and performs the necessary actions based on that information. Whether or not the user provides location information does not affect the process.
To ensure Turkish characters appear correctly after uploading your files to Netmera, ensure they are encoded in UTF-8 format before uploading them to the panel. This will resolve any issues with character rendering.
We have two methods to collect uninstall data:
Google and Apple services share uninstall data with Netmera, allowing us to obtain the information.
At Netmera, we receive device token information for your apps through Firebase Cloud Messaging (FCM). Tokens from devices that haven't connected to FCM for over 270 days become invalid. These tokens are linked to passive devices, which have likely been inactive for a long time. Messages sent to these old tokens won't be delivered.
Reasons for inactive tokens:
Devices lost, destroyed, or forgotten
Long periods of inactivity
If a token is inactive for 270 days, FCM marks it as invalid. Once a device reconnects, it gets a new token, and Netmera assigns a new installation ID. This process can lead to higher uninstall numbers, as previously successful message deliveries to these old tokens are now counted as failures. However, this change specifically impacts Android devices inactive for 270+ days.
No, such a feature is not currently available in Netmera.
No, it is not possible to send push notifications to a geofence via the REST API. However, you can create a geofence using the REST API.
Segments become inactive if no triggers occur for a segment within 90 days.
Yes, if a segment does not trigger a send via a push notification, even if the push notification is active, the segment becomes inactive.
Netmera uses cookies and browser-based user identification methods to track anonymous users on websites. Anonymous users are tracked with user IDs assigned to their browsers, which remain anonymous until the user logs in (or until an external ID is assigned). These user IDs persist as unique identifiers on the user’s browser until cookies are cleared.
Additionally, opt-in or opt-out mechanisms can be tracked via these user IDs, and web push notifications can be sent based on them. Anonymous users are associated with events (e.g., page visits, product views, searches), enabling the creation of segments for personalized notifications or experiences.
Yes, Netmera can track traffic sources through UTM parameters. These parameters can be sent to Netmera as events or attributes, providing insights into where users are coming from. For example:
UTM parameter: utm_source=facebook&utm_campaign=blackfriday
This information is stored as an event, allowing users to be segmented based on campaign data.
Open App: Triggered when the user visits the website.
Install (First Open) App: Triggered when the user visits the website for the first time.
Fancy Box Shown: Triggered when the Fancy Box (a pop-up asking for push notification permission) is displayed to the user.
Fancy Box Accept: Triggered when the user clicks the "Accept" button on the Fancy Box.
Fancy Box Later: Triggered when the user clicks the "Later" button on the Fancy Box.
Enable Push: Triggered when the user grants push notification permission.
Disable Push: Triggered when the user denies push notification permission.
Click Push: Triggered when the user clicks on a sent push notification.
Widget Shown Web: Triggered when a sent widget is displayed to the user on the website.
Widget Action Web: Triggered when the user clicks a link or a deeplink within a widget displayed on the website.
If you encounter issues with your widget displays, ensure that the file uploaded to your widget design is below 1 MB to optimize performance and compatibility.
The video size should not exceed 12 MB.
Generally, the information of targeted users can be obtained by exporting them from the Targeting > Segment section. By creating a segment and exporting the data, you can access the information.
The Netmera SDK tracks and reports various behaviors, including app installations, app openings, time spent in the app, push receipts, push opens, push dismisses, geofence enter/exit actions, location updates, actions taken inside web views presented by Netmera, log events (for errors), and more. You may visit Netmera Events for more information.
The default password expiration period is set to 90 days, requiring users to update their passwords every 90 days.
Yes, customers can modify the password expiration period on an app key or user-specific basis. To make these changes, they need to contact Netmera Support or their Customer Success Manager (CSM).
If a user does not log in for 30 consecutive days, the system will prompt the user to reset their password when they log in for the first time after this period.
If no activity occurs in the Netmera panel, the session will automatically time out after 30 minutes of inactivity. The user will need to sign in again to continue using the panel.
Select the "Keep Me Logged In" option at login. This keeps your session active without automatic logout, so you can maintain continuous access until you decide to log out manually.
Yes, bulk messages can be stopped midway. This is done by our operations team. Additionally, it is possible to a push notification from the panel.
Under the section, set the "Category" to "E-commerce" or "Media" to enable the catalog scenarios.
We can also determine the uninstall status of users through silent pushes. If the silent pushes do not reach the user (e.g., due to the device being in airplane mode or having no internet connection), the user is not marked as uninstalled. You may refer to for settings.
Yes, developers can trigger events with specific data when actions such as pressing the search button occur. For example, when a user performs a search (e.g., searching for hotels), an event is triggered, and the search query can be passed as an event attribute to track the search activity. For more details, visit: .
