How to check Campaign Reports ?

After launching, navigate to the 'Campaign' section to access logs and reports. Hover over the campaign name and select 'Go to Flow' to view detailed logs. For in-depth analytics, click on 'Analytics' to assess performance metrics and optimize future campaigns.

To view reports for a specific campaign, locate the desired campaign (e.g., 'Testing' campaign as shown in the screenshot below) and click on the analytics icon to access the campaign's full report

After clicking on the highlighted icon, you'll be taken to the analytics page for the whole campaign. You can check the delivery status (like Delivered, Failed, Rejected, Deduction, etc.). You can also apply a filter to view data for a specific date range.

To check the status of specific communications in a campaign, click on the 'Go to Flow' option. On the right side, you'll see the logs for all communications sent under that campaign.

Once the campaign is open, click on the highlighted icon to view the reports for specific communications sent. You can also use the date range filter here

You can also click on the eye icon to view the Node Info

Here, you'll find the status of the specific communication in the campaign, along with its unique Reference ID

To view the logs of all campaigns from your account, click on the 'Logs' option in the left-hand panel

From here, you can also access the analytics of any campaign by clicking on the 'Analytics' option.

The next option is 'API Failed Logs.' To view the failed campaign logs report, check the API Failed Logs

Common Issues Noted in Logs:

Incomplete Campaign Setup:
One common scenario where the API failed logs come into play is when a campaign is left in an incomplete state. This can occur for various reasons, such as missing information or incomplete configuration settings. The logs will capture this failure, allowing the user to revisit the campaign setup, identify the gaps, and correct them before re-executing the campaign.

Non-existent Slug:
Another situation that triggers a failed log is when the campaign references a slug that does not exist. Slugs are unique identifiers that help in accessing specific data or endpoints within the system. If a campaign is set to execute with an incorrect or non-existent slug, the API will fail to locate the necessary resources, resulting in a failed log entry. This serves as a prompt for the user to check and correct the slug, ensuring that the campaign is properly linked to the correct resources.

Inactive Campaign:
A campaign being in an inactive state is another common cause for failure. Inactive campaigns are those that have been disabled or are not currently active in the system. If an execution attempt is made on such a campaign, the API will log a failure. This is a safeguard to prevent the accidental execution of campaigns that are not ready to be deployed, prompting the user to either activate the campaign or re-evaluate its readiness for execution.

Conclusion

Campaign API Failed Logs are crucial for keeping your marketing campaigns on track. They provide alerts when something goes wrong, allowing you to fix issues like incomplete setups, incorrect slugs, or inactive campaigns. This helps ensure your campaigns run effectively and achieve their goals.