Data driven subscriptions also require the enterprise edition of SQL Server.

This is a bit of a roundabout solution but what I usually do is...

1.) Create a subscription for the report that is scheduled to only run once in the past. This way it will never actually be triggered by SSRS.

2.) All subscriptions in SSRS are actually SQL Server jobs. So I create a job on the SQL Server where the SSRS databases are located that runs the same SQL as the report and checks to see if any rows are returned. If there are then the job starts the job that equates to the SSRS subscription.

You can find the job that equates to the subscription by querying dbo.Subscriptions in the ReportServer database.